Keith Wall created QPID-7607:
--------------------------------
Summary: 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]
