You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2002/10/04 15:11:25 UTC
DO NOT REPLY [Bug 13287] New: -
INOUT parameters in WSDL-Driven call
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=13287>.
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=13287
INOUT parameters in WSDL-Driven call
Summary: INOUT parameters in WSDL-Driven call
Product: Axis
Version: current (nightly)
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: WSDL processing
AssignedTo: axis-dev@xml.apache.org
ReportedBy: acbellini@libero.it
I am accessing a MS Soap server using a direct AXIS Call. The operation which I
invoke has 4 IN parameters, 1 INOUT parameter and a result
If I manually set all 5 params and result, everything works fine, but if I
create the call based on WSDL information, the 5th parameter will be set as IN
instead of INOUT.
I found that Call.setOperation(QName, String) will take all input parts and set
them as IN parameters, while while output parts are discarded if they already
appear in IN parameters, and the first non-IN parameter is taken as result.
I have patched the code so that parts found both in input and output are set as
INOUT parameters.
I don't have access to any SOAP server that will use only OUT parameters, so I
just left subsequent non-IN parts to be discarded.
hope this helps