On 27 August 2014 23:16, xiaodan.wang <[email protected]> wrote:
> Hi Rob, > > Per your earlier question, with AMQP 0-10 we grabbed the queue name from > the > jms message as follows: > String queueName = ((Queue)message.getJMSDestination()).getQueueName(); > > With AMQP 0-91 had to make the follow change: > String queueName = > ((AMQTopic)message.getJMSDestination()).getRoutingKey().toString(); > > OK - I'll try to look into that tmr (my time) > Also, regarding this statement > >The 0.30 broker release provides some enhancements both to 0-9-1 > > functionality and message conversions between 0-9-1 and the other AMQP > > protocols. > > Does this mean that in pre-0.30 brokers a message enqueued by a AMQP 0-10 > client cannot be dequeued by a AMQP 0-91 client? > > No - just that the conversions have been improved. In particular for non-JMS compliant messages - messages with application headers which are lists. Such messages are not legal in JMS, but if a non-JMS client was sending pure AMQP they might arrive at the JMS client. Previously the 0-9 client didn't support the AMQP FieldArray type (roughly equivalent to list). In 0.30 that type is not supported in the message headers, but - as above - you can't legally use that from JMS. There has been conversion between 0-9 and 0-10 in place since the 0-10 protocol was first introduced. There have been a few updates since then to improve things as and when we've found things that could be improved. As long as you stick to legal JMS you should be good - improvements have (as far as I can remember) been around non-JMS corner cases. Hope this helps, Rob > Cheers! Dan > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7612668.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
