Also note that there is a DSL mechanism to mangle propagation of headers: http://camel.apache.org/how-to-avoid-sending-some-or-all-message-headers.html
2014-06-27 19:47 GMT+02:00 Matt Sicker <[email protected]>: > Thank you, that actually helped quite a bit! I see that using the in > message is just more convenient than copying headers all the time for an > InOut chain. > > > On 27 June 2014 00:44, Claus Ibsen <[email protected]> wrote: > > > Hi > > > > See this FAQ > > http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html > > > > If you have a copy of the Camel in Action book, see page 66 for more > > details as well. > > > > On Thu, Jun 26, 2014 at 10:44 PM, Matt Sicker <[email protected]> wrote: > > > I don't understand what the point of using the out message is. It > doesn't > > > copy headers. It doesn't signify the end of a route as far as I can > tell. > > > It's not used for a reply message. I don't think any of the official > > Camel > > > components even use the out message. What good is it for? > > > > > > In my own project, I've created a final processor that copies the in > > > message to the out message and selectively fills in headers that were > > > configured for that processor. I don't even know why I do this other > than > > > as a way to get rid of the myriad JMS headers that get passed around > from > > > using JMS (and occasionally rogue HTTP headers returned from a SOAP > call > > > somewhere). > > > > > > Are there any good resources or explanations as to the point of the out > > > message? It seems to complicate things as it doesn't seem as though you > > can > > > send a dual-message of anything by using both the in and out messages. > > > > > > -- > > > Matt Sicker <[email protected]> > > > > > > > > -- > > 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/ > > > > > > -- > Matt Sicker <[email protected]> > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
