axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajith Harshana Ranabahu (JIRA)" <>
Subject [jira] Commented: (AXIS2-696) ADB doesn't appear to support wildcard elements in the schema
Date Thu, 11 May 2006 09:08:05 GMT
    [ ] 

Ajith Harshana Ranabahu commented on AXIS2-696:

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

> ADB doesn't appear to support wildcard elements in the schema
> -------------------------------------------------------------
>          Key: AXIS2-696
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: databinding
>     Versions: 1.0
>  Environment: WinXP, JDK 1.5.06
>     Reporter: Simon Fell
>     Assignee: Ajith Harshana Ranabahu

> 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"
>                 </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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message