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 19:05 ------- I am using RPC/encoded. Continuing with my balls example from above, the WSDL for the array looks like: <complexType name="ArrayOf_tns2_TestBall"> <complexContent> <restriction base="soapenc:Array"> <attribute ref="soapenc:arrayType" wsdl:arrayType="tns2:TestBall[]"/> </restriction> </complexContent> </complexType> and the BallSack schema: <complexType name="BallSack"> <sequence> <element name="balls" nillable="true" type="impl:ArrayOf_tns2_TestBall"/> </sequence> </complexType> This all came from autogenerated WSDL from a while back. Is it incorrect? I've been doing some reading and am becoming quite suspicious of SOAP encoding in general and am considering abandoning RPC/encoded and going either RPC/literal or DOC/literal. Any references/examples for this shift would be appreciated.
