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-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
