| 1 |
|
| 2 |
==== README to examples/document/ |
| 3 |
|
| 4 |
Thomas Bayer granted use of his example under the ASF2 License. |
| 5 |
|
| 6 |
This directory contains four examples based on the same existing remote |
| 7 |
server. Sorry, the server thomas-bayer.com is not available anymore: |
| 8 |
the examples with the remote service will not work! |
| 9 |
|
| 10 |
The server published a nice WSDL file, and a separate schema, which |
| 11 |
have been beautified a bit but nothing more. |
| 12 |
|
| 13 |
. namesservice.wsdl |
| 14 |
The WSDL file, describing the service. |
| 15 |
|
| 16 |
. namesservice.xsd |
| 17 |
The Schema file, describing the data types transmitted. |
| 18 |
|
| 19 |
The examples explain how to communicate to the server using certain |
| 20 |
conditions: |
| 21 |
|
| 22 |
. has_wsdl.pl |
| 23 |
Shows how to use the WSDL file to access the server. Of course, this |
| 24 |
is by far the preferred way. |
| 25 |
|
| 26 |
. has_schema.pl |
| 27 |
Do not use the WSDL file, but only use the type definitions as found in |
| 28 |
the schema. Basically, a manual translation is made from the knowledge |
| 29 |
about the protocol (often found in some textual specification, when |
| 30 |
there is no WSDL) into the same structures as the WSDL produces. |
| 31 |
|
| 32 |
Besides the above intensively documented implementations, there are also |
| 33 |
two simplified implementations included in the package. Those may shape |
| 34 |
your own code, after you understand the structure. |
| 35 |
|
| 36 |
. has_wsdl2.pl is a simplification of has_wsdl.pl |
| 37 |
. has_schema2.pl is a simplification of has_schema.pl |
| 38 |
|
| 39 |
Please contribute. |