From Abstraction to Reality

WSDL bindings represent concrete connections.
WSDL also relies on XML Schema.

Thus, to define the concrete aspects of an operation, we use the WSDL binding element:

binding element- a WSDL SOAP extension element called soap:binding that is used to specify the transport protocol—such as HTTP, Simple Mail Transport Protocol (SMTP), or FTP—and whether we want clients to invoke a remote procedure call (RPC) at our site or just send an XML document.

To indicate to potential clients that they should invoke a method on our ZwiftBooks server, we add the style='rpc' attribute and value to the soap:binding element:

To define an operation, we add an operation element with the same name as the previously defined operation.
Within this operation element, we now add a soap:operation element with the soapAction attribute.
Finally, we must specify how the input and output messages of this operation are encoded.

The complete binding looks like this:

TheURI http://schemas.xmlsoap.org/soap/encoding/ indicates the SOAP encoding style as described in the SOAP specification.

WSDL file is complete and ZwiftBooks clients can begin to use it to figure out how to connect to the ZwiftBooks SOAP server and begin to use ZwiftBooks services.


Web Services Caveats Web services risks.




Maturity
Security
Transactions
Configuration Management