Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-696

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0
    • None
    • databinding
    • None
    • WinXP, JDK 1.5.06

    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.

      Attachments

        Activity

          People

            ajith Ajith Ranabahu
            sfell@salesforce.com Simon Fell
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: