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 04:23 ------- Actually, the metadata should indeed be set to the component class and not the array class in some cases. This is due, IIRC, to the somewhat weird way in which the BeanSerializer/Deserializer deals with indexed properties. This is some hairy and perhaps overly complicated code, however I am not yet convinced there is a bug with it. We have a bunch of tests which confirm that arrays of complex types work, including the SOAPBuilders interop suite and test.wsdl.arrays. I also just ran a couple of quick homebrew tests (starting from Java) of both web service methods returning arrays of beans and web service methods returning beans which contain arrays of beans. Both worked. Could you please attach a minimal test case which demonstrates the problem so we can reproduce it? Thanks!
