This section explains the purpose of the provided JMS serializer classes. Choose the serializer that handles the JMS message types that will be sent to the destination you are configuring.
For MapMessage messages, you create properties whose names match the message keys.
Both serializers support reading and writing application header properties and JMS header properties. The difference between the serializers is in how they handle payloads.
ByteMessageSerializer decodes the body as a sequence of bytes and parses them to create an XML structure according to the payload definition in the event. With
TextMessageSerializer, the text from the message is decoded as an XML string.
For incoming messages of type JMS BytesMessage, the serializer converts the message bodies to event payloads. The payloads are XML String type, but are not human-readable. However, you can access them using XPath functions.
For incoming messages, the TextMessageSerializer serializer converts JMS TextMessage messages to event payloads. The payloads are XML String type, and are human-readable. You can access them using XPath functions.