> On Wed, May 11, 2011 at 9:03 AM, Jens wrote:
>>
>> 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?
>>
>
> Take a look what your Exchange contains in that processor.
> And compare to the working example.I cannot really see a difference when looking at the exchange. However, I've been able to create a test case that produces this problem. When I simply add a throwException in the route, everything works as expected. If, like in my real-world case, the exception is thrown by a CxfEndpoint in the route, however, it doesn't. Please have a look at the attached test. Any feedback appricated. Thanks, Jens http://camel.465427.n5.nabble.com/file/n4387421/camel-exception-test.zip camel-exception-test.zip -- View this message in context: http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4387421.html Sent from the Camel - Users mailing list archive at Nabble.com.
