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=21389>. 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=21389 WSDL2Java complex type array handling broke in v1.1 (worked in v1.0) ------- Additional Comments From [EMAIL PROTECTED] 2003-07-08 12:03 ------- Andreas: Where did you get this WSDL? Did Axis generate it? If so, from what source? The WSDL is wrong, in that it uses a SOAP-encoded array (i.e. a ComplexType derived from soapenc:Array) in a doc/literal service. If instead you replace the "ArrayOfContact" complexType definition with: <complexType name="ArrayOfContact"> <sequence> <element name="item" type="impl:Contact" maxOccurs="unbounded"/> </sequence> </complexType> (a literal-style array), then this works just fine. We can look further into what the actual problem is, and try to generate a more reasonable error message (i.e. fail at WSDL2Java time in this situation). However if there's an issue with our WSDL generation, I'd like to know about it. So if you hand- crafted this WSDL, let us know. If you generated it using Axis, please include the source you started from in another attachment and we'll fix what's wrong. Thanks!
