[QPID-7607] AMQP 1.0 conversion layer to use 'Map' x-opt-jms-msg-type annotation when message is representable as a JMS Map Message and recipent known to be the Qpid JMS Client

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: qpid-java-broker-7.0.0
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 05/Jan/17 13:41
• Updated: 14/Nov/17 22:01
• Resolved: 14/Aug/17 13:01

Description

If the AMQP 1.0 converts a message for the Qpid JMS Client and the body is a Map whose content conforms to the JMSMapMessage restrictions (string keys, restricted domain of values etc), the conversion layer should set the “x-opt-jms-msg-type” annotation with a Map value so that the client, on receipt, will produce a JMS Map Message for the application.

For map messages converted from other protocols to AMQP 1.0, this will ensure fidelity (currently the user receives an ObjectMessage - see test org.apache.qpid.jms.provider.amqp.message.AmqpCodecTest#testCreateAmqpObjectMessageFromAmqpValueWithMap).

For management responses, this will ensure that many management responses can be handled simply.

If the map does not conform to the JMS restrictions or the client is not a Qpid JMS Client, the annotation must not be applied.

Q: how should the broker know the client understands the “x-opt-jms-msg-type” annotation?