On Thu, Jul 17, 2014 at 1:06 PM, RMA <[email protected]> wrote: > Hi Claus, > > First of all thank you very much for your answer. I've added some debug > (using "process" with "system.out") to my routes and I can confirm the > information you've given me. > > My new suspicious is now that the reply isn't sent as a JMS text message. In > my asynchronous routes I explicitly add the option "?jmsMessageType=Text" in > the "to()". I'll direct my investigation towards this new theory.
jmsMessageType=Text is only on the consumer side. If you want to reply back as text message, make sure the message body is text based, such as a String etc. You can use covertBodyTo(string.class) See on the JMS component page about mapping message body to JMS message types. > > Once again thank you very much for your help. > > Kind regards, > RMA > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Bridging-from-JMS-to-DIRECT-without-sending-the-JMS-Reply-in-the-DIRECT-tp5753926p5753959.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
