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)" <ji...@apache.org> on 2016/12/10 14:23:58 UTC
[jira] [Closed] (QPID-4992) preserve all AMQP properties in JMS
AMQP 1.0 API, so AMQP->JMS->AMQP works
[ https://issues.apache.org/jira/browse/QPID-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey closed QPID-4992.
-----------------------------
Resolution: Won't Fix
This client has been replaced by the new Qpid JMS library based on Proton
> preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP->JMS->AMQP works
> --------------------------------------------------------------------------
>
> Key: QPID-4992
> URL: https://issues.apache.org/jira/browse/QPID-4992
> Project: Qpid
> Issue Type: Improvement
> Components: JMS AMQP 1.0 Client
> Affects Versions: 0.22
> Environment: all
> Reporter: Axel Podehl
>
> As I understand from QPID-3380 there is no way to retrieve all AMQP header properties (e.g. contentType) with the Java API.
> In my case, I have a generic JMS record&replay program and would want to use it to record an AMQP message and replay it, simply using the QPid API, but unless I do some nasty type-casts, important AMQP properties are lost, for example AMQP content type.
> Interestingly enough, if I use the ActiveMQ transport transformer and receive AMQP messages through the ActiveMQ JMS API, all properties are copied for me:
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP
> So receiving an AMQP messages using the ActiveMQ JMS API gives me more information than with the Qpid AMQP JMS API, which is strange.
> Qpid's JMS API should be the expert on AMQP properties, not ActiveMQ's message transformer.
> Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties (https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP) in the QPid API itself ?
> Or at least have an option (e.g. in the ConnectionFactory) to do so ?
> That way a bridge of AMQP -> JMS -> AMQP wouldn't loose important information but could still stick with the real JMS API.
> Please note, it's quite common for JMS providers to extend the list of properties with a set of properties have a 'JMS' (or better a 'JMSX') prefix. For example MQ:
> http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fuj25450_.htm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org