I'm not sure, I hope there are others who can help you out better but I
think the error you're describing below would occur during unmarshalling
back to Java on the service-side, so if put your error-trapping logic in
an interceptor that occurs before the unmarshalling (
http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors),
you might be able to trap it there and forward a customized SOAP fault
back to the client. You may have to trace/debug the code a bit to find
out the exact interceptor phase to place this logic in (I don't know
myself, I have not done it before.)
Alternatively, more than a bit clumsy though, is to switch to the JAX-WS
Provider interface and work with pure XML, and raise whatever custom
exceptions you'd like.
Glen
On 08/06/2012 01:24 PM, Nathaniel Auvil wrote:
Can anyone help me out? Or is this not possible with cxf?
On Fri, Aug 3, 2012 at 2:22 PM, Nathaniel Auvil
<[email protected]>wrote:
how can i intercept xml validatoin errors coming out of the framework so
that i can return a custom error rather than a generic SoapFault?
Specifically, when i send a number in a boolean field, CXF errors out
before it ever gets to my service code. I am validating in my code versus
some configuration option to have CXF validate.
