Specifying namespaces in the Message Type property

When using the MRM domain, the Message Type property is used to specify the name of the message.

The format of a simple message type is {namespace-uri}:name where name is the name of the message, and namespace-uri. identifies the namespace. The namespace must be the full URI specification and must be enclosed in braces.

The format {namespace-uri}name (that is, with no colon) is also valid. This maintains compatibility with previous versions of the broker product.

If you omit {namespace-uri}, the first match for the name that is found in the model is used. You can do this if namespaces are not enabled for the message set, or if a name is unique within a message set. However, if a name is not unique, you must specify the namespace to be sure that the correct match is made in the model.

The following are examples of message types:

When identifying an embedded message using a message path, a message type path would be entered as A simple message type for a message in a real target namespace: {http://www.ibm.com/space}:name

The same name can occur in more than one namespace. To specify that a name is to be qualified with a specific namespace, the name must be prefixed with the namespace within the Message Type.

For example a Message Type with a single name would be entered as:
{http://www.ibm.com/space}:id/.../{http://www.ibm.com/space}:name
Related concepts
Namespaces in the message model
Identifying an embedded message using a Message Path
Namespaces with MRM XML messages
Namespaces with MRM non-XML messages
Reusing message definition files
Related tasks
Applying a Quick Fix to a task list error
Handling large MRM messages
Creating a message set
Creating a message definition file
Related reference
Message set properties
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:30

ad31040_