Glad to know you got it working! Feel free to file a JIRA ticket with your findings.
Regards, Raúl. On 1 Aug 2013, at 22:59, bocamel <[email protected]> wrote: > After I updated all Maven dependencies to the most recent version of Camel > and ActiveMQ (in my attempt to get rid of any incompatible servlet api jar), > the exception that happened after the return of my OutFaultInterceptor no > longer happens. The proper soap fault was returned to the client. Thank > you all for your help. > > Here is an observation I made... As Raul has suggested, I tried to do a > convertBodyTo (Document.class) immediately after receiving the PAYLOAD > message from CXF (in the from). Camel threw a CamelRuntimeException > immediately. It seemed to me that, Camel first tried to throw an > InvalidPayloadException as Raul predicted. But in the constructor of the > InvalidPayloadException, it tried to build the exception message from the > body using CxfPayload. That caused the subsequent runtime exception > (because the body is an ill-formed xml). If somehow Camel can collect > enough information to build the InvalidPayloadException without triggering > this new exception, all my functions can be done in Camel nicely without > messing with CXF. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736662.html > Sent from the Camel - Users mailing list archive at Nabble.com.
