Note the web services interface types
The client must identify parameter data types
<namesp1:sayHelloTo xmlns:namesp1="urn:HelloServer">
  <c-gensym3 xsi:type="xsd:string">Tim O'Reilly</c-gensym3>
</namesp1:sayHelloTo>
The server must identify return value data types
 <ns1:sayHelloToResponse 
 soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
   xmlns:ns1="urn:HelloServer">
   <sayHelloToReturn xsi:type="xsd:string">Hello Tim O'Reilly</sayHelloToReturn>
  </ns1:sayHelloToResponse>
The class definition's data types
public class HelloServer {
    public String sayHelloTo(String name) {
         return "Hello " + name;
    }
}
Study the request and response envelope contents for a moment here. Note that SOAP parameter and return types of the class (both Java String's) corresponds directly to the SOAP types in the request and response ("xsd:string").
Slide 34 of 58 Contents
  1 |   2 |   3 |   4 |   5 |   6 |   7 |   8 |   9 | 10
11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30
31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40
41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50
51 | 52 | 53 | 54 | 55 | 56 | 57 | 58
www.arachna.com > Educational Resources > Tutorials > O'Reilly Open Source Conference (2002) > Exchanging Objects and Messages With SOAP

spidaman
© 2002-2009 Ian Kallen | Copyright Notice