Ok, it’s actually other way around. The missmatch of header/property value with actuall Exception message comes with the fact that the shared UnitOfWork collects all the causes (CamelUnitOfWorkException) in the list and propagates only the first one (causes.get(0)) from the causes-list.
This can produce the wrong response that I’m having -> each splitted sub-exchange has ist own „request-id“ and it replies to the client with wrong exception-message for the given „request-id“. Not nice… any suggestions how to avoid this? Thanks, cheers, Boris -- View this message in context: http://camel.465427.n5.nabble.com/Headers-not-correctly-propagated-to-the-errorHandler-on-split-tp5741542p5741842.html Sent from the Camel - Users mailing list archive at Nabble.com.
