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=16180>. 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=16180 Axis only deserializing the first response parameter of document/literal call. ------- Additional Comments From [EMAIL PROTECTED] 2003-02-01 19:01 ------- I'm interested in resolving this bug also. The problem appears to be with handling multiple document/literal parameters in either direction (request or response). The code in BodyBuilder.java seems to handle this by constructing an initial RPCElement for the first parameter and then a SOAPBodyElement for each subsequent parameter. These subsequent parameters never get recognized when getParams() is called on the initial RPCElement (either in RPCProvider.processMessage() on the server side or Call.invoke() on the client side). My thought is to replay the parameter elements for document/literal messages in BodyBuilder.endElement() to populate the RPCElement with all the parameters. Does this sound right?
