Just want to highlight that I have my reservations on point 3. >From what I can see the ExchangePattern parameter doesn't determine anything. The same applies for calling something using inOut or inOnly.
Again from what I can see from the examples I have tried out, what determines if the parent route will wait or not for the sub-route to complete, or if the message used by the parent is the IN passed to the sub-route or the OUT of the sub-route ALL DEPENDS on if the sub-route, i.e. - if the sub route care less about the Exchange Pattern with which it has been called or not. I do not know if anyone can share an example where this is not so? DariusX wrote > 3. The MEP used for the "sub-route" determines whether the "parent" route > will wait for the "sub-route" and use the out-message of that sub-route as > the in-message to its next step. -- View this message in context: http://camel.465427.n5.nabble.com/Can-t-understand-what-inOnly-is-doing-tp5787961p5788103.html Sent from the Camel - Users mailing list archive at Nabble.com.
