>So I think its definitely worth revisiting what is an Exchange and >what should its contract be... I'm starting to wonder if its just a >context for the exchange (so you can access the IN) and a place in >which to register one or more OUT messages? > Would N out messages result in N exchanges for the next hop?
For WS-Addressing, where the original 'in' message is important, would it makes sense to stash the (important) in message in the exchange as a property. The pipeline will propagate exchange properties so the important in message will be visible from the pipeline to those who care. This may alleviate the need to traverse the set of chained exchanges to get a handle on the original in message. -- View this message in context: http://www.nabble.com/in-out-fault-messages-discussion-tp14170013s22882p15459603.html Sent from the Camel - Users mailing list archive at Nabble.com.
