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 06:21 ------- OK, this is obviously quite a complicated issue. I'm trying to figure out how to demonstrate clearly what we're seeing, but meanwhile, check this out. I *think* the problem might has something to do with sending/not sending XSI types. I have them turned OFF in my application (tighter XML, and helped bypass some odd interop bugs we were having). And when I turned them OFF in the test.wsdl.arrays example (by inserting the line [1] below into the autogenerated createCall method), that test failed immediately, with exception [2] below. Thoughts? [1] Line to disable sending of XSI types: _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, Boolean.FALSE); [2] Exception from server in test.wsdl.arrays with XSI types off in client: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild (SimpleDeserializer.java:189) at org.apache.axis.encoding.DeserializationContextImpl.startElement (DeserializationContextImpl.java:963) at org.apache.axis.message.SAX2EventRecorder.replay (SAX2EventRecorder.java:198) at org.apache.axis.message.MessageElement.publishToHandler (MessageElement.java:722) at org.apache.axis.encoding.DeserializerImpl.startElement (DeserializerImpl.java:404) at org.apache.axis.encoding.ser.BeanDeserializer.startElement (BeanDeserializer.java:165) ...
