wsdl2java not creating classes from unreferenced elements
---------------------------------------------------------

                 Key: AXIS2-5091
                 URL: https://issues.apache.org/jira/browse/AXIS2-5091
             Project: Axis2
          Issue Type: Bug
          Components: wsdl
    Affects Versions: 1.6.0
         Environment: WSDL 1.1
            Reporter: Iain Farrell
         Attachments: ExampleWsdl.wsdl

Trying to use wsdl2java and unreferenced elements are not being generated into 
classes.

In the schema I use [snippet below], only Abstract and AbstractType are 
generated; Concrete and ConcreteType are not, even though this is valid schema 
[and other WSDL to Java applications are able to create them]

The commandline I used was:
./wsdl2java.sh -uri "ExampleWsdl.wsdl" -o "./Output"

Using the -g flag does create the missing classes, but it does not create the 
build.xml file, which I require.

I have tried java 1.5.0_15 and 1.6.0_20, and Axis2 1.5.1, 1.5.5 and 1.6.0, all 
with the same results.

Schema snippet:
        <xs:complexType abstract="true" name="AbstractType">
          <xs:sequence>
                <xs:element name="Field" nillable="true" type="xs:string"/>
          </xs:sequence>
        </xs:complexType>
        
        <xs:complexType name="ConcreteType">
          <xs:complexContent>
                <xs:extension base="tns:AbstractType">
                  <xs:sequence>
                        <xs:element name="BaseField" nillable="true" 
type="xs:string"/>
                  </xs:sequence>
                </xs:extension>
          </xs:complexContent>
        </xs:complexType>
        
        <xs:element name="Abstract" type="tns:AbstractType" />

[apologies if I have set wrong options in the creation of this bug]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to