Do you mean as in real W3C SOAP faults?
That won't help, there isn't a real W3C SOAP fault - but CXF is
pretending that there is and (unless I've missed something) preventing
me from accessing the underlying IOException.
The situations in which I throw a proper SOAP fault are working just
fine (whether I throw one defined in the WSDL or not).
Jim
On 08/06/2012 19:11, Benson Margulies wrote:
Read up on SOAP faults?
On Fri, Jun 8, 2012 at 7:21 AM, Jim Talbut <[email protected]> wrote:
Hi,
How can my CXF client tell what type of thing went wrong?
I want to be able to classify faults into network faults and remote server
faults, because the response to the two is very different.
If I simply call the proxy with a few different failures all I get is a
SOAPFaultException with a cause of a SoapFault exception.
I was hoping that the network fault would have a root cause of some kind of
IOException.
This pair was caused by accessing a port that wasn't listening:
TestBrokenNetwork::test1] Exception: class
javax.xml.ws.soap.SOAPFaultException: Could not send Message.
TestBrokenNetwork::test1] Exception: class
org.apache.cxf.binding.soap.SoapFault: Could not send Message.
This was caused by an IllegalArgumentException thrown within the server
implementation:
TestLogging::testException] Exception: class
javax.xml.ws.soap.SOAPFaultException: You passed in the illegal word
TestLogging::testException] Exception: class
org.apache.cxf.binding.soap.SoapFault: You passed in the illegal word
This was caused by an explicit throw of a SoapFault by the server
implementation:
TestLogging::testSoapFault] Exception: class
javax.xml.ws.soap.SOAPFaultException: You passed in the triger word
TestLogging::testSoapFault] Exception: class
org.apache.cxf.binding.soap.SoapFault: You passed in the triger word
Is there any way to get more detail for classification?
Thanks.
Jim
