I see.
What I was planning to do was to handle the exception by storing information
about it in the database. Is it possible to use the Exception itself in the
route?
Of course I can handle this in the code (catch the Exception and store all I
need), but I thought it was better to just throw the Exception and then
handle it in the route.
Claus Ibsen wrote:
>
> Hi
>
> Yeah the sample is identical. But when the exchange fails, and onException
> is taking over, then it's the *original* exchange (= copy, aka snapshot)
> that is used, just before the node that fails.
>
> So its kinda like this
>
> from(fromRoute)
> TAKE SNAPSHOT (A)
> .beanRef("listTransformer", " fromStringToFundList initId")
> TAKE SNAPSHOT (B)
> .to("bean:fundListDao?methodName=save");
>
> So when the beanRef fails and onException is kicked in, then the exchange
> that is used there is from SNAPSHOT A. It need to do a SNAPSHOT when it
> does retries.
>
>
>
--
View this message in context:
http://www.nabble.com/Error-Handler-and-OutHeaders-tp19970966s22882p19971930.html
Sent from the Camel - Users mailing list archive at Nabble.com.
