[
https://issues.apache.org/jira/browse/QPID-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801604#comment-15801604
]
Rob Godfrey commented on QPID-7607:
-----------------------------------
So, this is for message conversion in general, so we'd want a message sent as a
JMS Map Message by a JMS 0-x client to come out as a JMS Map message on the 1-0
client (though if the producer had gine outside the JMS spec and added on
compliant types to the map, then they'd be out of luck)... Of course, with JMS
2.0 - as you point out - this is somewhat less of an issue since getObject()
can be used whatever.
For AMQP Management the issue is in some ways more with the 0-x client in that
it treats non-compliant maps as MapMessages and allow access to non-JMS
compliant types. If the 0-x client could also present these messages as an
ObjectMessage then perhaps things could be simplified.
> 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
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7607
> URL: https://issues.apache.org/jira/browse/QPID-7607
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Priority: Minor
> Fix For: qpid-java-7.0
>
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
