ws-savan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Walsh (JIRA)" <>
Subject [jira] Commented: (AXIS2-3655) Improper WSDL generation
Date Thu, 21 Oct 2010 21:32:16 GMT


William Walsh commented on AXIS2-3655:

I see a similar issue with Axis2 1.5.1 in that the WSDL produced via a browser (?wsdl) and
that produced via JavatoWSDL is different for InOnly operations.  The WSDL produced via the
browser doesn't work for us, but the WSDL from the tooling does work.  Should the WSDL be
equivalent?  For instance:

Fragment via the browser:
- <xs:element name="opIn">
- <xs:complexType>
- <xs:sequence>
  <xs:element minOccurs="0" name="opIn" nillable="true" type="xs:anyType" /> 

Fragment via the tooling:
            <xs:element name="opIn">
                        <xs:element minOccurs="0" name="args0" nillable="true" type="ax213:Axis2TypesStruct"/>

This looks like the same issue reported initially in this JIRA.


> Improper WSDL generation
> ------------------------
>                 Key: AXIS2-3655
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: wsdl
>    Affects Versions: 1.3
>         Environment: I used Axis2 v1.3 on JBossAS v4.0.5 running on Java 1.6.0_03.  I
used Windows XP.
>            Reporter: Nate Roe
>         Attachments:
> I have create a POJO service that returns a List<Person>.  
> The WSDL that is generated describes the service like so:
> <xs:element name="getPeopleResponse">
>   <xs:complexType>
>     <xs:sequence>
>       <xs:element minOccurs="0" name="return"
>           nillable="true" type="xs:anyType"/>
>     </xs:sequence>
>   </xs:complexType>
> </xs:element>
> whereas the element should probably actually state:
> <xs:element minOccurs="0" maxOccurs="unbounded" name="return" nillable="true" type="ns0:Person"/>
> That is, there should be "maxOccurs="unbounded"" and the type should be "ns0:Person"
instead of "xs:anyType".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message