Sorry, I never went the bean route, so I haven't looked too deeply into the error handlers behavior on it.
-----Original Message----- From: ychawla [mailto:[email protected]] Sent: Thursday, February 16, 2012 2:11 PM To: [email protected] Subject: RE: CXF + Camel + JMS Endpoint exception handling Hi Sven, Thanks for the reply. In my case, I am the client invoking a service that is down (at least in my test it is). According to the docs, I would be using the OUT phases: "When a CXF client invokes a CXF server, there is an outgoing interceptor chain for the client" I can see the exception in the PREPARE_SEND phase but not in any of the subsequent phases. Do you know of any other way I can get the CXF exception which in this case is a Connection Refused and propogate that to Camel so I can add a deadletter/redelivery strategy on it? Thanks, Yogesh -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-Camel-JMS-Endpoint-exception-handling-tp4471174p5490886.html Sent from the cxf-user mailing list archive at Nabble.com.
