[QPID-2363] JMS Map Message Should Support AMQP 0-10 Encoded Map As Message Body

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7
• Component/s: Java Tests, JMS AMQP 0-x
• Assignee: Rajith Muditha Attapattu
• Reporter: Rajith Muditha Attapattu
• Created: 26/Jan/10 20:44
• Updated: 14/Mar/17 20:07
• Resolved: 14/Apr/10 19:15

Description

As part of the new API initiative in Qpid, the C++ client and python client have added support for a map message, where the content is a map of key,value pairs encoded using the AMQP 0-10 encoding for Maps.
Currently the JMS Map message body is encoded as an opaque binary blob.
We need to add support for the JMS Map message implementation to set an AMQP 0-10 encoded Map for the message body.
This allows inteoperability btw JMS Map messages and c++, python map messages.
The content-type for the proposed map message is "amqp/map".

This feature is only added to the 0-10 code path as the versions below AMQP 0-10 does not have any native support for encoding maps.
The new map message format will be the default for any map message created by a 0-10 Session.
If it needs to send any messages using the old map message format it will need to use the following jvm arg "-Dqpid.use_legacy_map_message=true"
Once the addressing support is finalized we could also add a per destination flag to indicate if legacy messages needs to be used or not.