W3C home > Mailing lists > Public > xmlp-comments@w3.org > March 2002

Issue 16 closed: Void return type and no out arg

From: Murali Janakiraman <murali@roguewave.com>
Date: Mon, 4 Mar 2002 11:49:24 -0800
Message-ID: <F888C30C3021D411B9DA00B0D0209BE8014F46CD@cvo-exchange.cvo.roguewave.com>
To: "'xmlp-comments@w3.org'" <xmlp-comments@w3.org>
Cc: "'bryan_murray@HP.COM'" <bryan_murray@HP.COM>
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>"> 
        <StockName>Foo, inc.</StockName> 

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>"> 
                        xmlns:m="<http://example.org/2001/06/clock>" >

[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! :
Received on Monday, 4 March 2002 14:50:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:58 UTC