I've got a small server (not axis) and I'm testing interopability with an axis client (beta 1).
Parts of my wsdl file (I've also attached the real
file);
...
<types>
...
<complexType name="LoginError">
<sequence>
<element name="code" type="string"/>
</sequence>
</complexType>
...
</types>
...
<message name="LoginErrorMessage">
<part type="MyDefs:LoginError" name="loginError"/>
</message>
...
<operation name="LoginToService">
<input message="tns:LoginRequest"/>
<output message="tns:LoginResponse"/>
<fault name="LEM" message="tns:LoginErrorMessage"/>
</operation>
...
And a normal soap binding. A fault results in;
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns="http://www.eds.nl/ts1defs";>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<SOAP-ENV:faultcode>Server</SOAP-ENV:faultcode>
<SOAP-ENV:faultstring>Net.LoginError</SOAP-ENV:faultstring>
<SOAP-ENV:detail>
<LoginError><code>UU</code></LoginError>
</SOAP-ENV:detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Which looks about right. Looking at the wsdl spec
which says;
"The soap:fault element specifies the contents of the
contents of the SOAP Fault Details element"
Yet no LoginError exception is generated in axis (an
RemoteException is generated instead). The WSDL2Java
prog does generate the LoginError exception!.
Am I (or is my server) doing something wrong here ?
Arjen van Elteren
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
ts1.wsdl
Description: ts1.wsdl
