Show Table of Contents
1.5.11. Accessing AMQP Message Properties and Headers
The
message-id, correlation-id, user-id, subject, reply-to and content-type fields in the properties section of a 1.0 message can all be set or retrieved via accessors of the same name on the Message instance. The same is true of the durable, priority and ttl fields in the header section.
An AMQP 1.0 message has a
delivery-count field within the header section. There is no direct accessor for this field. However if the value is greater than 1, then the Message::getRedelivered() method returns true. If Message::setRedelivered() is called with a value of true, then the delivery count is set to 1, else it is set to 0.
The
application-properties section of a received 1.0 message is available via the properties map of the Message class. The properties map is used to populate the application-properties section when sending a message.
There are other fields defined in the AMQP 1.0 message format that do not have direct accessors on the
Message class.
The format for the keys is
x-amqp-<field-name>. The keys in use are: x-amqp-first-acquirer and x-amqp-delivery-count for the header section, and x-amqp-to, x-amqp-absolute-expiry-time, x-amqp-creation-time, x-amqp-group-id, x-amqp-qroup-sequence and x-amqp-reply-to-group-id for the properties section.
In addition the delivery- and message- annotations sections are available via a nested map with key
x-amqp-delivery-annotations and x-amqp-message-annotations respectively.
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.