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(); > > Is the destination that the message was sent to / the consumer that was created to receive the message a Queue or a Topic? I did a little test myself (sending to a queue object, receiving from a queue object) and the object that I got back from getJMSDestination() was a queue (and not a Topic as you seem to be getting)... however I did notice that the queue seemed to be in binding URL and not Address format - so I will try to fix that at least. -- Rob > 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? > > 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] > >
