Re: JMSDestination value different between 5.12.1 and 5.13.0

2017-03-29 Thread chiippy
Hi Tim This is the test code that I am using : from(triggerEndpoint) .setHeader("JMSXGroupID", constant("product1grp")) .to("amq:topic:VirtualTopic.producer.channel1.test") .setHeader("JMSXGroupID", constant("product2grp")) .to("amq:

Re: JMSDestination value different between 5.12.1 and 5.13.0

2017-03-29 Thread chiippy
Hi Tim Thanks for the reply. Yes, I can get the OriginalDestination via the ActiveMQMessage but no as ideal as we are using JMSDesintion for routing all over the places. Is there any way I can override JMSDestination at the consumer side by intercepting the incoming Message ? Any side effect ?

Re: JMSDestination value different between 5.12.1 and 5.13.0

2017-03-28 Thread Tim Bain
BTW, the page you linked to says "Set by the producer." Can you please provide the source for the statement that it's set by the consumer in 5.13.0? On Mar 28, 2017 9:35 AM, "Timothy Bish" wrote: > On 03/28/2017 10:32 AM, chiippy wrote: > >> Per the activeMQ message Properties definition : JMSD

Re: JMSDestination value different between 5.12.1 and 5.13.0

2017-03-28 Thread Timothy Bish
On 03/28/2017 10:32 AM, chiippy wrote: Per the activeMQ message Properties definition : JMSDestination However, since 5.13.0, the JMSDestination has been changed to be set by the Consumer instead of the Producer ? When using camel ac

JMSDestination value different between 5.12.1 and 5.13.0

2017-03-28 Thread chiippy
Per the activeMQ message Properties definition : JMSDestination However, since 5.13.0, the JMSDestination has been changed to be set by the Consumer instead of the Producer ? When using camel activemq, I have Producer : to("active