Hi All the MEPs is inherited from the JBI world. In reality there is only 2 which matters - InOnly (fire and forget) - InOut (request reply)
The MEP is just a "flag" on the Exchange. In reality end users of Camel should really just forget about the OUT message. Its also inherited from the JBI-world. Its just much easier to always just change/alter the IN message. The pipeline (pipes and filters EIP) is the default EIP pattern which is applied in Camel routes when you do from(X) to(A) to(B) to(C) So what happens is that A receives the output from X. The output is automatically copied by Camel as it detects if the Exchange has an OUT message, if not it re-uses the IN message. Likewise B receives the output from A, which again is either the OUT message or re-used IN message, and so forth. ======================== End users of Camel should really just forget about the OUT message. Its there for advanced use cases and to work with the JBI-world. ======================== We had discussions before whether or not to remove the OUT message, but it has always been part of Camel since 1.0 and due to the JBI-world, and we decided to keep it as is. On Mon, Sep 13, 2010 at 11:03 AM, Christian Mueller <christian.muel...@gmail.com> wrote: > > Hello Ashwin, hello Bengt! > > Thanks for your responses and the 2 cents :o) > Is it not confusing to provide exchange pattern in Camel which are not > supported (or differ from the spec), isn't? > > However, I think Ashwin you have more experience with Camel than I. Can you > (or somebody else) recommend whether a processor/type converter/... should > write the response into the in or out message? Or should this depend on the > exchange pattern (write the response into the out message if the exchange > out capable otherwise into the in message)? Or should the processor/... > throw an exception, if it receives an exchange which is not out capable and > the processors responsibility is to change the message? > My understanding of In-Only was a fire and forgot (I don't expect a > response). > > And I totally agree with Bengt, that this should be documented in the WIKI > (also how the pipeline works and the messages are copied from out to in) or > in the Camel in Action book. > > Cheers, > Christian > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Exchange-Patters-tp2836060p2837443.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
