Yes. I'm using camel v2.71.
Here is my error handler:
<errorHandler id="queryFormularyError" type="DeadLetterChannel"
deadLetterUri="direct:queryFormularyError" useOriginalMessage="true" />
and the deadletter route is:
<route>
<from uri="direct:queryFormularyError" />
<process ref="queryformularyErrorHandler" />
<to uri="bean:createReturnMsg" />
</route>
The queryFormularyErrorHandler refers to the QueryFormularyErrorHandler
processor described earlier, and the createReturnMsg bean just translates
the exception message into a format that can be returned to the caller.
I tried handling the error in the AggregatorStrategy, as described in the
Camel Book chapter 8, but that did not work. I couldn't get it to trap the
error at all. In the meantime, I've resorted to handling the error after
splitter/aggregator returns and transfers control to a new route, but I
would much prefer handling errors as they occur, in the splitter.
Thanks for your help.
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitter-StopOnException-doesn-t-forward-the-exception-on-the-Exchange-tp4469882p4473105.html
Sent from the Camel - Users mailing list archive at Nabble.com.
