tibemsMapMsg
Type
Remarks
Messages with this body type contain several values, indexed by name.
| Function | Description |
|---|---|
| tibemsMapMsg_Create | Create a map message. |
| tibemsMapMsg_Get | Get data values from a map message. |
| tibemsMapMsg_GetMapNames | Get an enumeration of the field names in a map message. |
| tibemsMapMsg_ItemExists | Test if a named pair exists. |
| tibemsMapMsg_Set | Set a name-value pair in a map message. |
| tibemsMapMsg_SetBytes | Set a byte array as a named value in a map message. |
Extensions
TIBCO Enterprise Message Service extends the JMS MapMessage and StreamMessage body types in two ways. These extensions allow TIBCO Enterprise Message Service to exchange messages with TIBCO Rendezvous and TIBCO SmartSockets programs, which have certain features not available within the JMS specification.
- You can insert another MapMessage or StreamMessage instance as a submessage into a MapMessage or StreamMessage, generating a series of nested messages, instead of a flat message.
- You can use arrays as well as primitive types for the values.
These extensions add considerable flexibility to the two body types. However, they are extensions and therefore not compliant with JMS specifications. Extended messages are tagged as extensions with the vendor property tag JMS_TIBCO_MSG_EXT.
For more information on message compatibility with Rendezvous messages, see "Message Body" in TIBCO Enterprise Message Service Release Notes.