[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805261#action_12805261
]
Rajith Attapattu commented on QPID-2363:
----------------------------------------
For the 1st iteration for testing I did have the encode and decode methods in
the AMQPEncodedMapMessage class.
Later on I changed it for the following reasons.
1. I wasn't really sure if there was sufficient interest for the new format for
apps using the 0-8 client.
2. Since all message implementations were version agnostic, I thought I'd
preserve that pattern. Therefore I used version specific delegates.
However I am not opposed to reverting to the previous version if you think
there is enough interest in using this in the 0-8 client.
> 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: Interop Testing, Java Client
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
