[AXIS2-1561] Java2WSDL generates incorrect WSDL

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: nightly
• Assignee: Deepal Jayasinghe
• Reporter: Manuel Ernstberger
• Created: 31/Oct/06 09:41
• Updated: 13/Jun/07 22:08
• Resolved: 13/Jun/07 22:08

Description

When I generate a WSDL from a Java class with the latest nightly build of Axis2, in the generated WSDL the "wsdl:fault" element has no "name" attribute, as it is supposed to be.

My Java class looks like that:

public class TestWSImpl implements TestWS {

public void ping(String text)

{ System.out.println(text); }

public String echo(String text)

{ System.out.println(text); return text; }

}

And this is the resulting WSDL:

<wsdl:definitions xmlns:axis2="http://epdm.tsystems.com/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ns1="http://epdm.tsystems.com/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://epdm.tsystems.com/xsd"><wsdl:types><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ax21="http://epdm.tsystems.com/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://epdm.tsystems.com/xsd">
<xs:element name="echoFault">
<xs:complexType>
<xs:sequence>
<xs:element name="echoFault" type="xs:anyType" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="echo">
<xs:complexType>
<xs:sequence>
<xs:element name="param0" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="echoResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="pingFault">
<xs:complexType>
<xs:sequence>
<xs:element name="pingFault" type="xs:anyType" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ping">
<xs:complexType>
<xs:sequence>
<xs:element name="param0" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema></wsdl:types><wsdl:message name="echoMessage"><wsdl:part name="part1" element="ns1:echo" /></wsdl:message><wsdl:message name="echoResponseMessage"><wsdl:part name="part1" element="ns1:echoResponse" /></wsdl:message><wsdl:message name="echoFault"><wsdl:part name="part1" element="ns1:echoFault" /></wsdl:message><wsdl:message name="pingMessage"><wsdl:part name="part1" element="ns1:ping" /></wsdl:message><wsdl:message name="pingFault"><wsdl:part name="part1" element="ns1:pingFault" /></wsdl:message><wsdl:portType name="TestWSPortType"><wsdl:operation name="echo"><wsdl:input message="axis2:echoMessage" /><wsdl:output message="axis2:echoResponseMessage" /><wsdl:fault message="axis2:echoFault" name="echoFault" /></wsdl:operation><wsdl:operation name="ping"><wsdl:input message="axis2:pingMessage" /><wsdl:fault message="axis2:pingFault" name="pingFault" /></wsdl:operation></wsdl:portType><wsdl:binding name="TestWSSOAP11Binding" type="axis2:TestWSPortType"><soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="echo"><soap:operation soapAction="urn:echo" style="document" /><wsdl:input><soap:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:input><wsdl:output><soap:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:output><wsdl:fault><soap:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:fault></wsdl:operation><wsdl:operation name="ping"><soap:operation soapAction="urn:ping" style="document" /><wsdl:input><soap:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:input><wsdl:fault><soap:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:fault></wsdl:operation></wsdl:binding><wsdl:binding name="TestWSSOAP12Binding" type="axis2:TestWSPortType"><soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="echo"><soap12:operation soapAction="urn:echo" style="document" /><wsdl:input><soap12:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:input><wsdl:output><soap12:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:output><wsdl:fault><soap12:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:fault></wsdl:operation><wsdl:operation name="ping"><soap12:operation soapAction="urn:ping" style="document" /><wsdl:input><soap12:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:input><wsdl:fault><soap12:body use="literal" namespace="http://epdm.tsystems.com/xsd" /></wsdl:fault></wsdl:operation></wsdl:binding><wsdl:service name="TestWS"><wsdl:port name="TestWSSOAP11port" binding="axis2:TestWSSOAP11Binding"><soap:address location="http://localhost:8080/axis2/services/TestWSTestWS" /></wsdl:port><wsdl:port name="TestWSSOAP12port" binding="axis2:TestWSSOAP12Binding"><soap12:address location="http://localhost:8080/axis2/services/TestWSTestWS" /></wsdl:port></wsdl:service></wsdl:definitions>

Issue Links

• relates to: AXIS2-2744 Testing RPCMessageReceiver with complex data using ADB generated test case