I believe there is a potential inter-op issue between AXIS2 generated
WSDLs and AXIS 1.1. Not sure if WSDL automatically generated by AXIS 2
engine is non complaint with SOAP 1.2 specification or whether SOAP
1.2 specification is not backward compatible with SOAP 1.1
specification.
When an AXIS 2 service throws a soap fault, following WSDL element
gets generated and it is not understood by AXIS 1.x wsdl2java tool.
Actual error message is captured below.
<wsdl:fault name="BankServiceException">
<soap:body use="literal"/>
</wsdl:fault>
However, if I manually alter the WSDL before generating the stubs
(using AXIS 1 wsdl2java tool), everything looks good.
<wsdl:fault name="GNSSystemException">
<wsdlsoap:fault name="GNSSystemException" use="literal"/>
</wsdl:fault>
java org.apache.axis.wsdl.WSDL2Java -- server-side --skeletonDeploy
true BankService.wsdl
- Unable to find required classes (javax.activation.DataHandler and
javax.mail.i
nternet.MimeMultipart). Attachment support is disabled.
java.io.IOException: ERROR: Missing <soap:fault> element inFault
"InsufficientFu
ndFaultMessage" in operation "InsufficientFundFaultMessage", in
binding withdraw
at org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(Symb
olTable.java:2858)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolT
able.java:2549)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:744)
at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543
)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:518)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
