camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From boday <ben.o...@initekconsulting.com>
Subject Re: Does onException not support multiple statements?
Date Wed, 11 May 2011 15:17:46 GMT
Jens, I do see that the exchange.getOut() message has a fault instead of just
an exception (in my example, etc).  This is causing the pipeline to
short-circuit.  Not sure if this is by design or not at the moment...I'll
poke around a bit.

To verify this, just add this line to your TestProcessor (though this is not
a solution by any means)...

exchange.getOut().setFault(false);


Jens wrote:
> 
> 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
> 


-----
Ben O'Day
IT Consultant -http://benoday.blogspot.com

--
View this message in context: http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4387637.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message