Claus, this is unfortunately not the same behavior we found out with the enrich processor (which also use the AggregationStrategy). We can reproduce the following behavior (with Camel 2.6): - If the exception is handled, the exception is not anymore set in the exchange (exchange.getException() as you suggested in your book doesn't work). We have to grab the exception from the exchange property Exchange.CAUSED_EXCEPTION. - If the exception is not handled, the AggregationStrategy is not called.
Please see also also my post at [1] where I got no response... :-(. Is this the expected behavior (and we have to document it) or should I raise a JIRA for it? Thank you in advance, Christian [1] http://camel.465427.n5.nabble.com/Behavior-of-AggregationStrategy-in-conjunction-with-the-enrich-DSL-the-onException-definition-and-ann-td3695716.html -- View this message in context: http://camel.465427.n5.nabble.com/aggregator-error-handling-default-does-not-propogate-error-tp4283684p4290872.html Sent from the Camel - Users mailing list archive at Nabble.com.
