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=12833>.
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=12833

Axis clients fail to extract the value of output (only) parameters when they are last 
in the parameter list.





------- Additional Comments From [EMAIL PROTECTED]  2002-09-23 19:59 -------
I found another problem that doesn't involve out only params and can be 
reproduced with a .NET server.

A .NET server method with the following signature:

public void HelloWorld( ref string inout1, ref string inout2,
                        ref string inout3, ref string inout4, string inonly)

in WSDL:

<s:element name="HelloWorld">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="inout1" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout2" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout3" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout4" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inonly" 
type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="HelloWorldResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="inout1" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout2" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout3" 
type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="inout4" 
type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>


Maps to this in the Axis client:

public java.lang.String helloWorld(javax.xml.rpc.holders.StringHolder inout1, 
javax.xml.rpc.holders.StringHolder inout2, javax.xml.rpc.holders.StringHolder 
inout3, java.lang.String inout4, java.lang.String inonly)

Notice how the last in/out turns into an in only and a return value is added.  
That’s pretty wired but not necessarily wrong.  But at runtime the parameter 
values get all jumbled between parameters and some are lost.

Let me know if you need the WSDL, client code and request reply dumps from 
TCPmon.

Reply via email to