You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2010/01/26 22:08:34 UTC
[jira] Commented: (QPID-2363) JMS Map Message Should Support AMQP
0-10 Encoded Map As Message Body
[ https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805201#action_12805201 ]
Rob Godfrey commented on QPID-2363:
-----------------------------------
I presume we are going to use a message header, or different mime type for the new header format...
that way the receiving client can determine whether it is an old style or new style map message without the application programmer having to know up front what type they should expect to receive. I'm happy with the default format on publish to be different between the 0-8 and 0-10 however I think we should find a better way than a JVM system property for specifying this - i.e. either per destination or per connection. I would actually -1 the idea of a system property as this seems entirely the wrong granularity for this option
> 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
>
>
> 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:dev-subscribe@qpid.apache.org