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
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 g...@redhat.com wrote:
On 07/15/2013
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
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
