Apache Axis WSDL2Java error - Missing <soap:fault> element

wsdl2java soapfault
Pearl picture Pearl · Jan 26, 2010 · Viewed 16.3k times · Source

We are integrating a third party SOAP web services in our application. The WSDL is used with SOAPUI tool, where sample requests and responses worked fine.

When we try to integrate with apache Axis 1.3, where we tried WSDL2JAVA with the WSDL. We received the following error

java.io.IOException: ERROR: Missing element inFault "serviceFault" in operation "serviceFault", in binding saveRegistration 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) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Unknown Source)

Anyone already faced this issue and solved?

Answer

ian_scho picture ian_scho · May 20, 2010

I believe that there is a JIRA open for this one.

Description:

When you have a soap 1.2 binding with soap fault, the fault element is not correctly extracted, resulting in error 

 ERROR: Missing <soap:fault> element inFault "..." in operation "...", in binding ...

Their temporary recommendation is adding a line of code and recompiling Axis1... Nahh.

Personally, I've just downloaded the wsdl file (it's an Axis 2 service and I have an Axis 1.5 client) and edited the namespace for all of the following lines from:

     <wsdl:fault name="Exception">
        <soap12:fault use="literal" name="Exception"/>
     </wsdl:fault>

to:

     <wsdl:fault name="Exception">
        <soap:fault use="literal" name="Exception"/>
     </wsdl:fault>

As suggested here.

Upgrading to Axis2, however, is the best long term solution. After resolving this issue, I have found yet more errors in the code that WSDL2JAVA has generated.

Related questions

Access restriction on class due to restriction on required library rt.jar?

I'm attempting to compile Java 1.4 code that was created by IBM's WSDL2Java on Java5 without recreating the stubs and saw this error in Eclipse. I'm under the assumption that the stubs generated should just compile as long as the …

Read More
How to avoid the need to specify the WSDL location in a CXF or JAX-WS generated webservice client?

When I generate a webservice client using wsdl2java from CXF (which generates something similar to wsimport), via maven, my services starts with codes like this: @WebServiceClient(name = "StatusManagement", wsdlLocation = "c:/some_absolute_path_to_a_wsdl_file.wsdl", targetNamespace = "…

Read More
Importing xsd into wsdl

This is my current configuration: XSD <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns="http://stock.com/schemas/services/stock" xmlns:tns="http://stock.com/schemas/services/stock" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="…

Read More