Hi, I have a CXF endpoint with a CXF interceptor that inspects properties from the Camel exchange in order to do its job. In the "good" case everything works fine: The properties/headers get set somewhere in the Camel route, and when the route finishes, the CxfBinding propagates them to the CxfExchange where the interceptor can find them.
If, however, the route is short-circuited by an exception, the propagation step from Camel exchange to CXF exchange seems to be skipped, and the information is not available to my interceptor. Any ideas on how to get that scenario to work without handling the exception in Camel? Thanks, Jens -- View this message in context: http://camel.465427.n5.nabble.com/camel-cxf-Accessing-Camel-headers-properties-in-CXF-interceptor-on-exception-tp5770530.html Sent from the Camel - Users mailing list archive at Nabble.com.