Thanks for your replay, Ben.
I just built a small test case similar to your example and it does indeed
work as expected.
Unfortunately, my real world case doesn't. Even if I replace proc3 by a
simple setBody("HelloWorld") the error route is shortcircuited before proc4
is called. It looks to me like Camel doesn't properly clean up the exchange
and still regards it as failed, therefore breaking out of the pipeline
again.
Any ideas what might be causing this?
Jens
--
View this message in context:
http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4386631.html
Sent from the Camel - Users mailing list archive at Nabble.com.
