[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

[Josh Carlson]

Hi Steve,

I was wondering if this fix appears in the 1.1 client? It doesn't appear 
to be in the release notes 
https://www.vmware.com/support/vfabric-rabbitmq/doc/vfabric-rabbitmq-rn-3.2.html#resolvedissues-rjms

Thanks

Josh

On 09/18/2013 06:57 AM, Steve Powell wrote:
> 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 
> <http://www.rabbitmq.com/>,//Pivotal <http://gopivotal.com/>]
> /“L’enfer, c’est les autres.” /Sartre
>
> On 17 Sep 2013, at 20:21, Josh Carlson <josh.carlson at kaazing.com 
> <mailto: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/20131210/5fda9a82/attachment.html>