Claus, no luck...I don't even see the JMSXGroupID header property displayed
using the "log:test?showHeaders=true" approach...
Exchange[Headers:{JMSType=null, JMSCorrelationID=null,
JMSMessageID=ID:BODAY-2278-1251924072421-2:19:1:1:396, JMSE
xpiration=0, JMSRedelivered=false, JMSDeliveryMode=2, JMSPriority=4,
JMSTimestamp=1251924275937, JMSReplyTo=null,
JMSDestination=queue://GatewayMsgQueue},
BodyType:String, Body:<inbound><test/></inbound>}
I was however, able to get this value set appropriately using a
servicemix-jms component using an overridden
JMSProviderMarshaler.createMessage() method.
The questions remains...why didn't the approaches I used in Camel set this
value appropriately?
thanks again...
Claus Ibsen-2 wrote:
>
> Hi
>
> Take a look at this unit test on trunk
> https://svn.apache.org/repos/asf/camel/trunk/components/camel-jms/src/test/java/org/apache/camel/component/jms/JmsRouteUsingJMSXGroupTest.java
>
> You can change the foo logger to show headers with: showHeaders=true
> And then you should see the JMXSGroupID logged.
>
> You can try that with Camel 1.6.x to see how it goes there.
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
-----
Ben - Senior Consultant
--
View this message in context:
http://www.nabble.com/unable-to-set-JMSXGroupID-using-ServiceMix-Camel-tp25249635p25265459.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
