Issue 16 closed: Void return type and no out arg

Hi all and Bryan,

  Issue 16 [1] is closed as proposed in message [2].

 In a nut shell, the following explanation and the examples below captures
the resolution. For more details, read message [2].

 The existence of a return value is signified by the presence of a
namespace-qualified accessor named 'result' with the namespace identifier
"<http://www.w3.org/2001/12/soap-rpc>" and void returns are not expected to
have the above named accessor. 

Example 1: An example of an envelope with a successful RPC response of a
procedure with a return value and an [out] parameter.

<env:Envelope xmlns:env="<http://www.w3.org/2001/06/soap-envelope>"> 
  <env:Body> 
    <m:GetLastTradePriceResponse 
 
env:encodingStyle="<http://www.w3.org/2001/06/soap-encoding>" 
                        xmlns:m="<http://example.org/2001/06/quotes>" 
                        xmlns:r="<http://www.w3.org/2001/06/rpc>"> 
        <r:result>34.1</r:result> 
        <StockName>Foo, inc.</StockName> 
    </m:GetLastTradePriceResponse> 
  </env:Body>
</env:Envelope> 

Example 2: An example of an envelope with a successful RPC response of a
procedure with a void return value and no out or inout parameters.

<env:Envelope xmlns:env="<http://www.w3.org/2001/06/soap-envelope>"> 
  <env:Body> 
    <m:SetDateResponse 
 
env:encodingStyle="<http://www.w3.org/2001/06/soap-encoding>" 
                        xmlns:m="<http://example.org/2001/06/clock>" >
    </m:SetDateResponse> 
  </env:Body>
</env:Envelope> 


[1] http://www.w3.org/2000/xp/Group/xmlp-issues#x16

 [2] http://lists.w3.org/Archives/Public/xml-dist-app/2002Feb/0231.html


Rogue Wave User Conference in Vail, Colorado, July 2002! :
http://www.roguewave.com/corp/events/usersgroup/

Received on Monday, 4 March 2002 14:50:45 UTC