Body Types

EMS follows Jakarta Messaging in defining five types of message body:

• tibemsMapMsg  

  The message body is a mapping from field names to values. Field names are strings. EMS supports an extended set of values types (extending Jakarta Messaging). Programs can access fields either by name, or sequentially (though the order of that sequence is indeterminate).

• tibemsObjectMsg  

  The message body is one serializable object.

• tibemsStreamMsg  

  The message body is a stream of values. Programs write the values sequentially into the stream, and read values sequentially from the stream.

• tibemsTextMsg  

  The message body is one character string (of any length). This text string can represent any text, including an XML document.

• tibemsBytesMsg  

  The message body is a stream of uninterpreted bytes. Programs can use this body type to emulate body types that do not map naturally to one of the other body types.