I have a functioning webservice that has both Java and .Net client. I'm
having some difficulty with user-defined faults. I have an operation
with a fault called NoSuchContract in my WSDL. WSDL2Java generates a
NoSuchContractFault that extends org.apache.axis.AxisFault implements
java.io.Serializable.
When the Java client calls the web service, it catchs the user-defined
fault (NoSuchContractFault). However, in SOAPMonitor I see the request
and then there is no response. The fault is not being returned in a SOAP
Envelope for some reason...
in my client, after the webservice is called e.dumpToString() gives ->
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString:
faultActor:
faultNode:
faultDetail:
{urn:bah:contract:0.1:types:fault}NoSuchContractFault:
<Message>Contract -1 does not exist</Message>
{http://xml.apache.org/axis/}exceptionName:
myfaultpackage.NoSuchContractFault
This is what I was expecting - but I was expecting there to be a SOAP
response.
Any idea why the user-defined fault is not coming back as SOAP?
I'm going to try this:
http://marc.theaimsgroup.com/?l=axis-user&m=106910146416788&w=2 -
Creating a class that extends RemoteException and implements
Serializable.
Any input or suggestions would be helpful.
Thanks,
Ann
