Resolution:
Description:
============

The destination deserializer (both BytesMessageSerializer and TextMessageSerializer) converts the JMS message BODY to event payloads.
The value of the event@payload depends on the JMS message type and if you have defined a payload or not.

For JMS Bytes Message,

- If there is no payload defined for the event then it gives a non-human readable representation of the body of the message.

Ex: [B@19abd2b

- If there is payload defined for the event then it gives a human readable representation of the body of the message.

Ex:

&ltEmployee>
    &ltName&gtEswar</Name>
    &ltDept&gtSupport</Dept>
</Employee>

For a JMS Text Message, it always returnss a human readable representation of the body of the message, even if you do not define a payload.

Ex:

&ltEmployee>
    &ltName&gtEswar</Name>
    &ltDept&gtSupport</Dept>
</Employee>

Note that this is just a string representation of the payload. If you want to access the payload using the XPATH functions you will need to define a payload for the event.

Environment:
============

   o TIBCO BusinessEvents 3.0.1
   o All OS