axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9665] New: - minOccurs/maxOccurs not being used by WSDL2Java
Date Thu, 06 Jun 2002 14:18:51 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9665>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9665

minOccurs/maxOccurs not being used by WSDL2Java 

           Summary: minOccurs/maxOccurs not being used by WSDL2Java
           Product: Axis
           Version: beta-2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: jeff.edwards@fmr.com


The minOccurs / maxOccurs attribute are not being analyzed by the WSDL2Java 
tool. The generated JavaBean is always the same regardless of the maxOccurs 
value -- the tool assumes a value of 1. For example I tested the following:

<element name="Book">
    <complexType>
        <sequence>
            <element ref="Chapter" minOccurs="1" maxOccurs="10" />
        </sequence>
    </complexType>
</element>

This generates the bean Book with a member of type Chapter. The singular 
containment of Chapter by Book is unexpected since the multiplicity is defined 
to be 1 to 10.  The generated JavaBean Book should contain some sort of 
java 'Collection' of Chapter data types.

Mime
View raw message