On Thu, Sep 1, 2011 at 6:31 PM, Jens <smix...@dzbank.de> wrote: > koseki nonuyuki wrote: >> I encountered the same trouble when I got SOAP fault. >> >> The first processor in the onException route, I put >> "exchange.getOut().setBody(null)" , then multiple >> process worked. >> >> When onException route received SOAP fault, the outMessage already >> contains Exception info, that >> cause another Exception at the next process and rollback, I guess. > > I'm doing the same thing, plus > > exchange.setProperty(Exchange.EXCEPTION_CAUGHT, > exchange.getOut.getBody()); > > before that so the exception remains accessible. It seems to me that's what > the onException handler should do already, though. >
SOAP Faults is not part of the Camel error handling by default. There is a handle fault (interceptor) you can enable which turns a SOAP Fault -> Exception, which the Camel error handler will be abel to detect and react upon. > Jens > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4759049.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
