RE: SOAP Method Return Type.

["Brown, Keith" <KB...@develop.com>]

The server that exposes the SOAP endpoint specifies two schemas: one for the
request message and one for the response message, so unless you build in
some application-level hints, you'll just get the return value as defined in
the response message schema.
 
By applying the xsi:type attribute to the GetLastTradePrice element, you've
specified that GetLastTradePrice is an integer as opposed to a structure
with one accessor (symbol).
 
What made a big difference to me in understanding SOAP was thinking less
about RPC and more about messaging - each SOAP request is simply a
serialized object graph. Each SOAP response is also a serialized object
graph. As a result, the SOAP/Perl bits reflect this thinking (hopefully for
the better). The SOAP/Perl bits from a year-and-a-half-or-so ago (0.9) that
required CDL to operate was purely an RPC-based approach and was much harder
to implement.
 
Keith
http://www.develop.com/kbrown <http://www.develop.com/kbrown> 

-----Original Message-----
From: Kailash Aynor [mailto:kail_list@hotmail.com]
Sent: Thursday, August 17, 2000 1:58 PM
To: SOAP; soap-dev@xml.apache.org
Subject: SOAP Method Return Type.


Hi,
 
I would like to know, whether Client can specify the method return type that
it is expecting. SOAP Spec says that "The name of the return value accessor
is not significant. ". But what about the return type. What I would like to
see is a request send by the client as:
 
<SOAP-ENV:Body>
       <m:GetLastTradePrice xmlns:m="Some-URI" xsi:type="xsd:int">
           <symbol>DEF</symbol>
       </m:GetLastTradePrice>
   </SOAP-ENV:Body>
 
Is this syntax currently supported? Or, is it taken for granted that
whatever the server provides(as return value), client accepts it and
converts internally ??
 
Also I think such a mechanism would help in implementing one-way calls.
 
Thanx.
Kail.