- From: David Fallside <fallside@us.ibm.com>
- Date: Fri, 13 Jul 2001 12:53:06 -0700
- To: "Bob Cunnings" <cunnings@lectrosonics.com>
- Cc: xml-dist-app@w3.org
Bob, as you have noted, this issue is already on our issues list, and so we
are committed to deal with it. Unless you think there is something missing
from the existing description of that issue, we will leave it as is.
Thanks,
............................................
David C. Fallside
XMLP WG Chair
Ext Ph: 530.477.7169
fallside@us.ibm.com
"Bob Cunnings"
<cunnings@lectros To:
onics.com> cc:
Sent by: Subject: Re: Publication of the first W3C Working Drafts of SOAP
xml-dist-app-requ Version 1.2 and of the XML Protocol Abstract Model
est@w3.org
07/13/2001 09:56
AM
Hello,
After reading the 1.2 version spec for SOAP, I wish to renew
previous concerns about Section 7.1 "RPC responses" [1].
Specifically, there seems to be no provision for the case of method
signatures with a void return. As it stands, the first accessor in the
response is assumed to contain or reference a return value. The
situation results in confusion when the method signature contains
a void return and one or more "out" parameters... the first accessor
is treated as the return, rather than as the first "out" param.
This area needs clarification, as real world implementation
experience has proven it to be troublesome.
The question: what is the representation for a response with a void
return, possibly with "out" or "in,out" parameters?
The matter was placed on the the XMLP issues list and has id
"16". [2]
Thanks,
RC
[1]http://lists.w3.org/Archives/Public/xml-dist-
app/2000Aug/0002.html
[2] http://www.w3.org/2000/xp/Group/xmlp-issues#x16
Received on Friday, 13 July 2001 15:52:25 UTC