Show Table of Contents
20.6. Java JMS Message Properties
The following table shows how Qpid Messaging API message properties are mapped to AMQP 0.10 and 1.0 message properties and delivery properties.
Table 20.3. Mapping JMS Headers to AMQP fields
| JMS Header Name | AMQP Identifier | AMQP Field | AMQP Section | Notes |
|---|---|---|---|---|
JMSCorrelationID | correlation_id
| correlation-id
| properties | |
JMSDeliveryMode | delivery_mode
| durable
| header | Computed value: [durable ? 'PERSISTENT' : 'NON_PERSISTENT'] |
JMSDestination | to
| to
| properties | |
JMSExpiration | absolute_expiry_time
| absolute-expiry-time
| properties | |
JMSMessageID | message_id
| message-id
| properties | |
JMSPriority | priority
| priority
| header | |
JMSRedelivered | redelivered
| delivery-count
| header | computed value: delivery-count > 0 |
JMSReplyTo | reply_to
| reply-to
| properties | |
JMSTimestamp | creation_time
| creation-time
| properties | |
JMSType | subject
| subject
| properties |
Note
As per the JMS specification; Message header field references are restricted to:
JMSDeliveryModeJMSPriorityJMSMessageIDJMSTimestampJMSCorrelationIDJMSType
When using JMS only these fields are strictly valid in a selector.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.