As well as the missing name attribute, there is also the problem
that it is a <soap:body>, whereas wsdl2Java expects a <soap:fault> .
I've noticed there are already at least 2 bug reports on JIRA regarding
this, so I won't raise a new one:
http://issues.apache.org/jira/browse/AXIS2-2295
http://issues.apache.org/jira/browse/AXIS2-2294
thanks,
Stuart
The name attribute is required in a <soap:fault> declaration. If Axis2
generated the WSDL, then this is a bug. Please file a JIRA.
Anne
On 4/3/07, Stuart Owen <[EMAIL PROTECTED]> wrote:
Hi,
I have a colleague who has generated a webservice using Axis2. I'm
not sure of the exact specifics of how the service was generated, but I
believe it was using 1.1.1 version which I understand is the latest.
However, I have problems when I try to use the service using Axis1 (the
java version 1.4 which I believe is the latest), which is forced upon me
for various reasons. When I run wsdl2Java I get the following error:
java.io.IOException: ERROR: Missing <soap:fault> element inFault
"updateFault" in operation "updateFault", in binding update
at
org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(SymbolTable.java:2858)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolTable.java:2549)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:744)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
I've looked at the wsdl and in the soap11 bindings it defines the fault
as follows:
<wsdl:fault name="updateFault">
<soap:body use="literal" />
</wsdl:fault>
whereas I would expect
<wsdl:fault name="updateFault">
<soap:fault use="literal" name="updateFault" />
</wsdl:fault>
which is what the error message suggests.
I've looked at the SOAP 1.1 spec and as far as I can understand a
wsdl:fault should contain soap:fault with matching names.
So is this an incompatibility between Axis1 or 2, or a genuine problem?
Is there a way of forcing Axis2 to generate an Axis1 compatible WSDL, or
vice versa?
thanks for any help,
Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
