[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2363:
------------------------------
Component/s: (was: Interop Testing)
Java Tests
> JMS Map Message Should Support AMQP 0-10 Encoded Map As Message Body
> --------------------------------------------------------------------
>
> Key: QPID-2363
> URL: https://issues.apache.org/jira/browse/QPID-2363
> Project: Qpid
> Issue Type: New Feature
> Components: Java Client, Java Tests
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
> Attachments: QPID-2363.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
