DO NOT REPLY [Bug 9882] New: - WSDL with single output and parameterOrder generates bad stub.

[bugzilla]

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

WSDL with single output and parameterOrder generates bad stub.

           Summary: WSDL with single output and parameterOrder generates bad
                    stub.
           Product: Axis
           Version: current (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Basic Architecture
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Given:

<message name="outRequest"/>
<message name="outResponse">
  <part name="varString" type="xsd:string"/>
</message>


...
  <operation name="echoOut" parameterOrder="varString">
    <input message="tns:outRequest"/>
    <output message="tns:outResponse"/>

  </operation>
...

The generated signature is:

public void echoOut(StringHolder varString) throws RemoteException
;

But the stub code itself does not fill in the returned value.  I suspect it 
should be looking at whether the given parameter is unlisted or not (see 
parameterOrder in JAX-RPC 4.3.4 for definition of unlisted parameters).  This 
output parameter is listed.  If it WERE unlisted, the signature would have 
looked like:

public String echoOut() throws RemoteException;

The processing of the return in the stub seems to assume this is the 
signature.