A Mule flow has a JMS queue listener as the message source. Where can the next message processor access a JMS message's header?

A Mule flow has a JMS queue listener as the message source. Where can the next message processor access a JMS message's header?

• A. Outbound property
• B. Inbound property
• C. Message property
• D. Transport property

Answer: (B)

When a JMS message arrives from the queue, its headers (the metadata the JMS transport provides) are exposed to the flow as inbound properties. The next processor in the Mule flow can read those values from inbound properties, which is exactly how you access JMS headers after the message is received. Outbound properties are for values you set to influence how a message is sent out, not for reading what came in. Message properties correspond to custom, user-defined data on the message, and transport properties relate to the transport’s own configuration rather than the JMS headers. So the JMS header you want is read from inbound properties, for example via inboundProperties['JMSCorrelationID'].

When a JMS message arrives from the queue, its headers (the metadata the JMS transport provides) are exposed to the flow as inbound properties. The next processor in the Mule flow can read those values from inbound properties, which is exactly how you access JMS headers after the message is received. Outbound properties are for values you set to influence how a message is sent out, not for reading what came in. Message properties correspond to custom, user-defined data on the message, and transport properties relate to the transport’s own configuration rather than the JMS headers. So the JMS header you want is read from inbound properties, for example via inboundProperties['JMSCorrelationID'].