Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
Message exchange patterns and the Exchange objectThe Camel API is influenced by APIs such as JBI specification, CXF which defines a concept called Message Exchange Patterns (MEP for short). The MEP defines the messaging style used such as one-way (InOnly) or request-reply (InOut), The Exchange API provides two methods to get a message, either Flow of an exchange through a route
Beware of getOut to check if there is an out message exchange.getOut creates an out message if there is none. So if you want to check if there is an out message then you should use exchange.hasOut instead Using getIn or getOut methods on ExchangeNow suppose you want to use a Camel Processor to adjust a message. This can be done as follows: public void process(Exchange exchange) throws Exception { String body = exchange.getIn().getBody(String.class); // change the message to say Hello exchange.getOut().setBody("Hello " + body); } This seems intuitive and is what you would expect is the right approach to change a message from a Processor. public void process(Exchange exchange) throws Exception { String body = exchange.getIn().getBody(String.class); // change the message to say Hello exchange.getOut().setBody("Hello " + body); // copy headers from IN to OUT to propagate them exchange.getOut().setHeaders(exchange.getIn().getHeaders()); } Well that is not all, a Message can also contain attachments so to be sure you need to propagate those as well: public void process(Exchange exchange) throws Exception { String body = exchange.getIn().getBody(String.class); // change the message to say Hello exchange.getOut().setBody("Hello " + body); // copy headers from IN to OUT to propagate them exchange.getOut().setHeaders(exchange.getIn().getHeaders(); // copy attachements from IN to OUT to propagate them exchange.getOut().setAttachments(exchange.getIn().getAttachments()); } Now we ensure that all additional data is propagated on the new OUT message. But its a shame we need 2 code lines to ensure data is propagated. public void process(Exchange exchange) throws Exception { String body = exchange.getIn().getBody(String.class); // change the existing message to say Hello exchange.getIn().setBody("Hello " + body); } Consider using getIn As shown above you most often need to alter the existing IN message, than creating a totally new OUT message. Changing the IN message directly is possible in Camel as it doesn't mind. Camel will detect that the Exchange has no OUT message About Message Exchange Pattern and getOutIf the Exchange is using So the example code above is possible for any kind of MEP. The MEP is just a flag on the Exchange which the Consumer and Producer adhere to. |