DO NOT REPLY [Bug 16842] New: - WSDL2Java generates unusable classes for Arrays

[bu...@apache.org]

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=16842>.
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=16842

WSDL2Java generates unusable classes for Arrays

           Summary: WSDL2Java generates unusable classes for Arrays
           Product: Axis
           Version: 1.1beta
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: gauwin@campus.dtrd.de


I'm trying to use this array :

<xsd:complexType name="strSeq">
   <xsd:complexContent>
       <xsd:restriction base="SOAP-ENC:Array">
           <xsd:sequence>
               <xsd:element name="item" minOccurs="0" maxOccurs="5"
type="xsd:string"/>
           </xsd:sequence>
           <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:string[]"/>
       </xsd:restriction>
   </xsd:complexContent>
</xsd:complexType>

but the file generated by WSDL2Java doesn't contain the getItem() and
setItem(...) methods (so this class is unusable).

I've made some tests to find the cause, and it works when I remove the
<complexContent> and <restriction> tags.

However, the original WSDL seems correct (I've found the same structure in the
soap specification).