axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Lawson (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2022) WSDL2Java baulks at legitimate maxOccurs="unbounded"
Date Sat, 18 Jun 2005 18:01:18 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2022?page=comments#action_12313986 ] 

Jeff Lawson commented on AXIS-2022:
-----------------------------------

BTW, -w also fixes issue 2023.


> WSDL2Java baulks at legitimate maxOccurs="unbounded"
> ----------------------------------------------------
>
>          Key: AXIS-2022
>          URL: http://issues.apache.org/jira/browse/AXIS-2022
>      Project: Apache Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.2, 1.2.1
>  Environment: Windows 2000 Professional; Java 1.4.2-b28
>     Reporter: Jeff Lawson

>
> This pattern:
> <element name="MyElement" type="abc:MyType"/>
> <complexType name="MyType">
>   <sequence>
>     <element ref="abc:MyOtherElement" minOccurs="0" maxOccurs="unbounded"/>
>   </sequence>
> </complexType>
> causes WSDL2Java to throw:
>     java.io.IOException: Type {http://ay-bee-cee/}MyOtherElement is
> referenced but not defined
> maxOccurs="unbounded" is causing the problem because this pattern:
> <element name="MyElement" type="abc:MyType"/>
> <complexType name="MyType">
>   <sequence>
>     <element ref="abc:MyOtherElement" minOccurs="0"/>
>   </sequence>
> </complexType>
> does not throw an exception, though it's too far from what I want. I discovered, however,
that this pattern:
> <element name="MyElement" type="abc:MyType"/>
> <complexType name="MyType">
>   <sequence>
>     <element ref="abc:MyUnwantedElement" minOccurs="0"/>
>     <element ref="abc:MyOtherElement" minOccurs="0" maxOccurs="unbounded"/>
>   </sequence>
> </complexType>
> didn't throw an exception either and it produced code from which I could easily remove
MyUnwantedElement-related content.

-- 
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


Mime
View raw message