A Message Type may contain a simple message identifier or a message type path when defining multipart messages. When defining multipart messages the Message Type is combined with the Message Type Prefix message set property. A message type path may also be specified when using the FolderBitStream option of the ESQL ASBITSTREAM function and CREATE ... PARSE statement.
The format of a simple message type is 'id' where 'id' is the identifier of the message. The format of a message path is '/id1/..../idm' where 'id1' is the identifier of the outermost message and 'idm' the identifier of the innermost message or element.
It is possible that the same identifier may occur in different namespaces. To specify that an identifier is to be qualified with a specific namespace, the identifier must be prefixed with the namespace within the Message Type. The namespace must be the full URI specification and be enclosed in braces.
For example a Message Type with a single identifier would be entered as:
{http://www.ibm.com/space}id
and with a message type path
{http://www.ibm.com/space}id/.../{http://www.ibm.com/spacem}idm
If no namespace is specified for an identifier the first match found in the model will be used. Therefore if namespaces are not enabled, or an identifier is unique within a message set, the namespace need not be specified in the Message Type. If an identifier is not unique, you should specify the namespace to ensure that the correct match is made in the model.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad31040_ |