You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/08/14 13:02:01 UTC
[jira] [Commented] (QPID-7607) 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
[ https://issues.apache.org/jira/browse/QPID-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125651#comment-16125651 ]
Keith Wall commented on QPID-7607:
----------------------------------
QPID-7434 changed the conversion layer. {{x-opt-jms-msg-type}} is now set for converted stream or map messages, regardless of the client, if the content complies within the JMS restrictions for those messages types.
> 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-broker-7.0.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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org