camel-cxf leverage the CXF soap stack by redirect the invocation of the
method to the camel route.
ServiceMix is using the cxf-bc to handle the transport lever work and
cxf-se to parser the soap message.
On 4/6/12 10:24 AM, Castyn wrote:
I actually do have validation enabled on the CXF consumer in the properties
with the schema-validation-enabled which I guess is why it returns a SOAP
fault to the calling client and not something else.
I didn't realize a CXF consumer never technically enters a route unless the
consumer parse is successful, that is good to know. I know I can generate
and view faults once in the route or even after the CXF Producer in my route
that happens later, I was just hoping for more of a window into the entire
pipeline.
Any ideas why Servicemix generates so much error text for a SOAP fault or
how to make it less verbose?
--
View this message in context:
http://camel.465427.n5.nabble.com/Detecting-SOAP-Faults-tp5618665p5621874.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
