WSDL is platform and language independent: WSDL is not tied into one
programming language and platform. WSDL-based web services could be
developed and deployed in Microsoft's .NET environment and consumed
via Java GUI applications. Alternately, WSDL-based web services could
be developed and deployed in a Java environment and consumed via
PHP-based web applications.
WSDL describes services in an abstract fashion: services are described
in an abstract fashion as they help to promote loose coupling and aid in
developing against interfaces, promoting good design.
??? ???
???
Chapter 6
[ 117 ]
WSDL binds services to concrete protocols: the specific binding for a service
is separated from the description of the service because loose coupling
between services and their transports is enabled.
WSDL is extensible: WSDL does not tie communications to one specific
protocol, for example SOAP over HTTP. As new transport mechanisms are
required, additional bindings can be specified. Today, we may only need
to access our WSDL described services via SOAP, but in the future we may
need JMS or SMTP bindings. WSDL format allows us to extend WSDL
documents to add additional bindings as and when necessary.
The Format of WSDL Documents
Now that we've described what WSDL is and the benefits that it gives, lets take a
look at what WSDL documents look like.
Pages:
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117