Message Mapping in TIBCO Rendezvous
TIBCO Rendezvous messages are composed of header information and a set of message fields. The header information is directly mapped to message context properties.
Message Field Elements
A message field is composed of the following elements:
Element | Description |
---|---|
Name | Character string. Does not have to be unique in a message. |
Identifier | Short integer. Unique in a message. Implicitly limits the number of message fields to 65535. The scope of the identifier is the message (or sub message). The same identifier can be used in two sub-messages, which are themselves part of a containing message. |
Value | The message field data. |
Count | Number of items (in the case of an array) |
Type | The type of the message field. |
Mapping Process
TIBCO Rendezvous structured messages are mapped to XML elements in the following way:
Name is used as the element name. The TIBCO Rendezvous field name may contain characters that are not valid for use in XML element names. The adapter generates valid character mappings between XML and TIBCO Rendezvous structured messages.
Identifier is put into an ‘id’ attribute.
Value contains a string representation that is the body of the element.
Count is ignored.
Type information is put into an xsi:type attribute for the generated element.
For more information, see Data Type Mapping for Receive Handlers in TIBCO Rendezvous.
See Also
TIBCO Rendezvous Concepts
Creating TIBCO Rendezvous Receive Handlers