You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Axel Podehl <ax...@gmail.com> on 2013/07/15 18:38:04 UTC
JMS API incomplete ?
Hi all,
as I understand from a previous post and from my testing, there is no way to
retrieve all AMQP header properties (e.g. contentType) just using the JMS
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
<https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP>
So receiving an AMQP messages using ActiveMQ JMS API gives me more
information than the Qpid AMQP JMS API...
Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties
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 and could stick with the real JMS API.
Axel
--
View this message in context: http://qpid.2158936.n2.nabble.com/JMS-API-incomplete-tp7595272.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: JMS API incomplete ?
Posted by Axel Podehl <ax...@gmail.com>.
Ok, great - any idea what time-frame this might be implemented by ?
--
View this message in context: http://qpid.2158936.n2.nabble.com/JMS-API-incomplete-tp7595272p7595407.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: JMS API incomplete ?
Posted by Rob Godfrey <ro...@gmail.com>.
Work on a complete JMS mapping is underway, in conjunction with the OASIS
AMQP Bindings and Mappings Technical Committee. There will be a way to
access all properties directly or indirectly once this is complete.
-- Rob
On 16 July 2013 12:57, Gordon Sim <gs...@redhat.com> wrote:
> On 07/15/2013 05:38 PM, Axel Podehl wrote:
>
>> Wouldn't it make sense to deploy the same mapping of AMQP to JMS
>> properties
>> in the QPid API itself ?
>>
>
> I would agree.
>
> [FWIW the c++ qpid::messaging API does something similar. I.e. all AMQP
> 1.0 properties etc that do not have direct accessors in the Message class
> can be accessed via special keys (e.g. x-amqp-to, x-amqp-first-acquirer
> etc)].
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.**org<us...@qpid.apache.org>
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: JMS API incomplete ?
Posted by Gordon Sim <gs...@redhat.com>.
On 07/15/2013 05:38 PM, Axel Podehl wrote:
> Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties
> in the QPid API itself ?
I would agree.
[FWIW the c++ qpid::messaging API does something similar. I.e. all AMQP
1.0 properties etc that do not have direct accessors in the Message
class can be accessed via special keys (e.g. x-amqp-to,
x-amqp-first-acquirer etc)].
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org