[ http://issues.apache.org/jira/browse/AXIS-466?page=all ]
     
Davanum Srinivas resolved AXIS-466:
-----------------------------------

     Assign To:     (was: Axis Developers Mailing List)
    Resolution: Cannot Reproduce

not enough info to recreate the problem. please upload complete wsdl (after 
testing with Axis 1.2 RC3 or latest CVS) and i will reopen the bug.

thanks,
dims

> wsdl2java tool schema compatibility failure
> -------------------------------------------
>
>          Key: AXIS-466
>          URL: http://issues.apache.org/jira/browse/AXIS-466
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.0
>  Environment: Operating System: All
> Platform: All
>     Reporter: Andras Avar

>
> There is a problem on generating java interface classes from wsdl. The 
> elements 
> that are represented by extension base in schema are placed  after  the 
> extension elements.
> The schema specification says the representation of extension base and 
> extension are oredered and the extension is placed at the end of the message.
> ***************************************
> Let's have an example:
> - Here is a schema with an extension:
> <xs:complexType name="submitReqType">
>       <xs:complexContent>
>               <xs:extension base="tns:genericVASPRequestType">
>                       <xs:sequence>
>                               <xs:element name="Recipients" 
> type="tns:recipientsType"/>
>                               <xs:element name="ServiceCode" 
> type="tns:serviceCodeType" minOccurs="0"/>
>                               ...
>                               <xs:element name="DistributionIndicator" 
> type="xs:boolean" minOccurs="0"/>
>                               <xs:element name="Content" 
> type="tns:contentReferenceType" minOccurs="0"/>
>                       </xs:sequence>
>               </xs:extension>
>       </xs:complexContent>
> </xs:complexType>
> <xs:complexType name="genericVASPRequestType">
>       <xs:annotation>
>               <xs:documentation>Base type for all requests from VASP to 
> R/S</xs:documentation>
>       </xs:annotation>
>       <xs:sequence>
>               <xs:element name="MM7Version" type="tns:versionType"/>
>               <xs:element name="SenderIdentification" 
> type="tns:senderIDType"/>
>       </xs:sequence>
> </xs:complexType>
> - The bad xml representation produced by the generated interface look like 
> this:
>   <SubmitReq 
> xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-
> 1-1">
>         <Recipients>
>         <To>
>                 <RFC2822Address xsi:nil="true"/>
>                 <Number displayOnly="false">+420</Number>
>                 <ShortCode xsi:nil="true"/>
>         </To>
>         </Recipients>
>         ...
>         <Content href="cid:CFA2D105D249AE505148EEFEC5473D1F"; 
> allowAdaptations="true"/>
>         <MM7Version>5.3.0</MM7Version>
>         <SenderIdentification>        
>                 <SenderAddress>+358990000003/PLMN</SenderAddress>
>         </SenderIdentification>
>   </SubmitReq>
> ***************************************

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to