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=13355>. 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=13355 Type info in body is validated even if use=literal [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-02-17 02:57 ------- The xsi:type on your array element (i.e. <ConfigurationArray>) looks wrong, in a couple of different ways. First of all, the schema in the WSDL specifies a "literal" collection, i.e. an element with maxOccurs="unbounded". This being the case, the xsi:type of the ConfigurationArray element should, if anything, be "s0:ArrayOfCounfiguration". SOAP encoded arrays shouldn't be anywhere in the picture here. Second, even if SOAP-encoded arrays WERE in the picture, SOAP-ENC:arrayType is NOT a valid type - that qname is reserved for the arrayType attribute, which itself contains the qname of the array component type. Marking this INVALID for now. If you can reduce this to a valid test case which demonstrates a particular failing of Axis, please open another bug with that specific test. Thanks!
