Name
JMSType — Purpose: Identification
JMSType is an optional header
set by the JMS client. Its name is somewhat misleading because it has
nothing to do with the type of message being sent (BytesMessage, MapMessage, etc.). Its main purpose is to
identify the message structure and type of payload; it is only
supported by a couple of vendors.
Some MOM systems (e.g., IBM’s WebSphere MQ) treat the message body as uninterpreted bytes and provide applications with a simple way of labeling the body (the message type). So the message type header can be useful when exchanging messages with non-JMS clients that require this type of information to process the payload.
Other MOM systems (e.g., Sun’s JMQ) directly tie each message to some form of external message schema, and the message type is the link. These MOM systems require the message type because they provide metadata services bound to it.
In addition, the JMSType
might be used on a application level. For example, a messaging
application that uses XML as its message payload might use the
JMSType to keep track of which XML
DTD the message payload conforms to. However, since the JMSType can possibly be used by JMS vendors,
it would be much safer to use application properties, which are
discussed in detail in Appendix C.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access