ADB doesn't appear to support wildcard elements in the schema

• Key: AXIS2-696
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Ajith Harshana Ranabahu
• Reporter: Simon Fell
• Component/s: databinding
• Affects Version/s: 1.0

Description

using the WSDL from AXIS2-694

ran WSDL2Java -s -u -uri partner.wsdl

the WSDL includes an xsd:any on the definition of SObject, which doesn't appear to have made it into the SObject class, this may be related, the QueryResult complexType ends up with the records array being declared as an OMElement array, not an SObject array. (Axis2-694 stops me from seeing if this array contains anything useful), from the schema
            <complexType name="sObject">
                <sequence>
                    <element name="type" type="xsd:string"/>
                    <element name="fieldsToNull" type="xsd:string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
                    <element name="Id" type="tns:ID" nillable="true" />
                    <any namespace="##targetNamespace" minOccurs="0" maxOccurs="unbounded" processContents="lax"/>
                </sequence>
            </complexType>

            <complexType name="QueryResult">
                <sequence>
                    <element name="done" type="xsd:boolean"/>
                    <element name="queryLocator" type="tns:QueryLocator" nillable="true"/>
                    <element name="records" type="ens:sObject" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
                    <element name="size" type="xsd:int"/>
                </sequence>
            </complexType>

If ADB doesn't support these schema constructs, it should fail with a useful error message during WSDL2Java.

Comments

[Ajith Harshana Ranabahu]

Fixed. The issue was in handling imported types in the schema compiler. Will resolve the issue once the SVN is up and the change committed

Fix in latest SVN.

thanks,
dims