Hello Jared! If you have to propagate the body to a downstream service, you have to care about the body. You have to make sure the body has a format ActiveMQ can serialize (String, byte array, map, ...). Otherwise, how should ActiveMQ be able to send your body over the wire?
Best, Christian ----------------- Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Jul 29, 2013 at 11:20 PM, jduncan <jdun...@iqnavigator.com> wrote: > I have a route that listens on an ActiveMQ endpoint and only manipulates > exchange headers. I don't care about the body of the exchange at all. > Consequently, I don't want to have to > marshal/unmarshal/serialize/deserialize the body at all, but just send it > along to anything downstream. Particularly, I don't want to try and > deserialize object messages in case I do not have the serialized class in > my > classpath. I have tried adding the mapJmsMessage=false property to my AMQ > consumer, but when I do that a null body gets passed to any downstream > routes. > > How can I pass along the original body without touching it at all? > > Thanks! > Jared > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-route-only-dealing-with-headers-tp5736452.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
