like this flipped back and forth a
> few times, I just want to make sure I have it right (for latest release).
>
You only need the end() in the last doCatch or doFinally.
You dont need an end on the doTry as it knows it ends when doCatch comes.
> --
> View this message i
doTry()...doCatch()..end()..end() or is it doTry()..doCatch()..end() ? From
reading the commit comments it appears like this flipped back and forth a
few times, I just want to make sure I have it right (for latest release).
--
View this message in context:
http://camel.465427.n5.nabble.com/doTry
doCatch to be called. This works in all cases except for the postprocess_it
> subroute. If I can cut out the aggregate and go straight to the postprocess
> subroute, then it works, so I know the aggregator is "handling" the
> exception, the doCatch does not
ception, the doCatch does not get called, but the doFinally does.
I need your help in identifying what camel-fu is needed around the aggregate
so that it doesn't try to handle the exception and just let it bubble up to
the parent's doCatch.
thanx in advance!
--
View this message in context:
http://camel.465427.n5.nabble.com/doTry-doCatch-with-an-aggregate-tp5581510p5581510.html
Sent from the Camel - Users mailing list archive at Nabble.com.
