- From: Bob Cunnings <cunnings@lectrosonics.com>
- Date: Tue, 28 Oct 2003 16:16:24 -0700
- To: <www-ws-desc@w3.org>
Hello, FWIW, a voice from the crowd in the bleachers: It was not so long ago the issue of indicating return values in WSDL 1.1 descriptions of SOAP RPC operations proved a big headache for those working on WSDL1.1/SOAP1.1 interop (viz. soapbuilders). The parameterOrder attribute in WSDL 1.1 could be exploited to do so indirectly, but had the weakness that it was an optional attribute. There were also problems on the SOAP side w.r.t. distinguishing return value accessors from other [out] parameters. At the time it was fervently hoped that succeeding versions of both specs would provide improvements in these areas, and of course SOAP 1.2 took care of this with rpc:result. The issue at that time was not one of distinguishing between, [in] and [out] parameters, but one of distinguishing between return values and other [out] parameters. So if the rpc style is to be supported by WSDL 2.0, then historical experience, if nothing else, may suggest that it would be a good idea to define a simple mechanism to specify the return value component of an RPC signature, to improve interop. This one bit of information can help WSDL aware RPC deserializers immensely. RC
Received on Tuesday, 28 October 2003 18:16:47 UTC