[rabbitmq-discuss] When using rabbitmq-jms javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card

[Steve Powell]

Thanks Josh,

This indeed appears to be a bug.  [I go to the trouble of serialising and deserializing the destination and then overwrite it with the Consumer’s destination before returning it!]

I will raise an internal bug and should have this corrected in the next release. Should you require further support this should be requested through the usual vFabric channels.

Steve Powell  [Cell: +44-7815-838-558] [RabbitMQ, Pivotal]
“L’enfer, c’est les autres.” Sartre

On 17 Sep 2013, at 20:21, Josh Carlson <josh.carlson at kaazing.com> wrote:

> When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card. I have tested with both 1.0.3 and 1.0.5 clients with RabbitMQ 3.1.5.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130918/c8f5bc28/attachment.htm>