Export
When exporting an EMS message, tibemsd translates it to a Rendezvous message with the following structure.
- The field
JMSHeaders
contains a submessage; see Jakarta Messaging Header Fields. When the transport parameterexport_headers
isfalse
, this field is omitted. - The field
JMSProperties
contains a submessage; see Jakarta Messaging Property Fields. When the transport parameterexport_properties
isfalse
, this field is omitted. - When translating the data fields of an EMS message, the results depend on the Jakarta Messaging body type. The following table specifies the mapping.
Jakarta Messaging Body Type | Export Translation |
---|---|
BytesMessage
|
The message data translates to a byte array that contains the bytes of the original EMS message. The field |
TextMessage
|
The message data translates to a UTF-8 string corresponding to the text of the original EMS message. The field |
ObjectMessage
|
The message data translates to a byte array containing the serialized Java object. The field |
StreamMessage
|
The message data translates to a byte array that encodes the objects in the original EMS message. The field |
MapMessage
|
The message data fields map directly to top-level fields in the Rendezvous message. The fields retain the same names as in the original EMS message. See also, EMS Extensions to Jakarta Messaging Messages. |