Web Service Description Language WSDL Detailed (3)

Namespace and child nodes are namespace properties:

Each NameSpace property declares a thumbnail and in the document. For example, "XMLns: XSD" is defined for http://www.w3.org/2001/xmlschema defines an abbreviation (XSD). This allows for the Namespace to add a prefix before the name, such as "XSD" in "XSD: int" is the legal type name. Normal scope rules can be applied to a thumbnail prefix. That is, the elements defined by the prefix are only valid in the elements.

What is the name of the NameSpace? The role of NameSpace is to avoid naming conflicts. If I build a web service, where the WSDL file contains an element named "foo", and you want to use my service with another service connection as a supplement, the other service WSDL file cannot be Contains an element named "foo". The two servers can only take the same name only when they represent exactly the same thing in both instances. If there is a difference in Namespace, "foo" in my network service can represent the meaning of "foo" completely different from another network service. In your client, you can quote my "foo" as long as you restrict.

See here: http://www.infotects.com/fooservice#foo is a fully restricted name, which is equivalent to "Carlos: foo", if I declare Carlos as http://www.infotects.com/fooservice fast the way. Note that the URL in NameSpace is used to determine their uniqueness, and it is also easy to position. Where the URL points to the URL does not have to be the actual network address, or the GUID can be used instead or complement the URL. For example, GUID "335DB901-D44A-11D4-A96E-0080AD76435D" is a legal NAMESPACE assignment. The TargetNameSpace property declares a namespace, all the names of all the declarations in the element are listed in it. In the WSDL example, TargetNameSpace is http://tempuri.org/wsdl. This means all the names declared in the WSDL document belong to this namespace. element has its own targetNameSpace property, its value http://tempuri.org/xsd, all the names defined in the element belong to this Namespace rather than Main's target namespace.

The following lines of the element declare the default Namespace. All valid names in Schema belong to this namespace.

XMLns = http://www.w3.org/2001/xmlschema

SOAP Messages For clients and services using WSDL, a way to study the WSDL file is to determine what to accept the information sent. Although SOAP uses the underlying protocol, such as IP and HTTP, etc., the application determines the advanced protocols interacting between the server and the client. That is, one operation is performed, for example, "echoint" sends the input integer back, the number of parameters, the type of each parameter, and how the parameters transmits and other factors determine the application specific protocol. There are many ways to determine such protocols, but I believe the best way is to use WSDL. If we use this perspective to look at it, WSDL is not just an interface protocol, and it is a specific language of protocol. It is our application specific protocol that we exceed "fixed" protocol (IP, HTTP, etc.). WSDL can determine if the SOAP message follows the RPC or document style. The RPC style message (that is, used in the example) looks like a function call. And document-style messages are more common, and the nested levels are smaller. The following XML message is the example WSDL file resolution sent / acceptable effect, parsing the SOAPCLIENT object in MS SOAP Toolkit 2.0 (MSTK2). Call from the client "Foo (5131953)" function:

5131953 Accepted by the server: , as described in WSDL, is a single parameter. Fooresponse has a portion of the . Note that EncodingStyle, Envelope, and Message's Namespace and WSDL Bindings columns are repeated as follows: