Parsing Web Interface Description Language WSDL (4)

Web

The WSDL design inherits the open design philosophy of contemporary web technology standards based on XML. It allows the use of other type definition languages (not just XMI schemas) by extension, allowing the use of multiple network transport protocols and message formats (not only soap/http, http-get/post, and MIME defined in the specification). WSDL also applies the concept of reuse in contemporary software engineering, separating the abstract definition layer and the concrete deployment layer, which greatly increases the reusability of the abstract definition layer.

1. SOAP Binding

The WSDL includes bindings for SOAP 1.1 terminals, which support the following protocol information specifications:

You need to indicate that this binding is for the SOAP 1.1 protocol.
The way to specify an address for a soap terminal.
The URI used to soapaction the HTTP header, which is the HTTP header that is bound to soap.
A header list definition that is passed as part of the soap wrapper.

The SOAP binding extends the WSDL using the following extension elements: (note in bold)





Encodingstyle= "Uri-list" namespace= "uri" ... 3
... 4


Encodingstyle= "Uri-list"? Namespace= "uri"/> ... 3
... 4


Encodingstyle= "Uri-list" namespace= "uri" ... 5




... 6

1) soap:binding

The purpose of the SOAP binding element is to indicate that the binding is in the SOAP protocol format: Envelope, Header, and body. This element does not declare an encoding or message format. You must indicate the soap:binding element when using SOAP binding.

2) soap:operation

The Soap:operation element provides information for the operation as a whole.

The Style property indicates whether the operation is oriented to RPC (message contains parameter and return value) or document oriented (message contains document). This information can be used to select the appropriate programming template. The value of this property affects how the SOAP message body is built, and defaults to the value specified in the Soap:binding element if no value is specified. If the soap:binding element does not specify a style, it is assumed to be "document."

The SOAPAction property specifies a value for the SOAPAction header for this operation. This URI should be used directly as the value of the SOAPAction header, and do not attempt to turn a relative URI into an absolute URI when making a request. This value is required for the HTTP protocol that is bound to soap (it has no default value). For other SOAP protocol bindings, a value cannot be specified for it, and the soap:operation element can be ignored.