10-05-2014, 11:34 AM
Web Services Description Language (WSDL)
Web Services Description.pdf (Size: 176.79 KB / Downloads: 67)
What WSDL is for
When you create a service, you typically do it
because you want other people to use it.
In order for them to do that, they need to know
what information to send to the service, what
information the service is going to send back, and
where to find the service in the first place.
It is much more helpful to have a standard,
preferably human- and machine-readable, format
for this information.
WSDL Data Structure
WSDL does not presume that exchanges
will take place using a particular form of
communication
Different services could combine
different interfaces using different
binding, and could make them available at
different addresses
Port and Service
A service may have more than one endpoint,
with each one defined by its own port
element.
The port element corresponds to a particular
binding, and includes information on how to
access it (URI).
Different ports represent different bindings for
the same port type – allows the same
functionality to be accessible via multiple
transport protocols and interaction styles
WSDL and Other
Standards
Generic service description language – WSDL
Specific standards
Electronic Data Exchange (EDI) used in manufacturing
SWIFT used in financial world
Possibility
Hybrid : other standards + WSDL
Independent
WSDL as a wrapper for these standards so that the
systems that support them become Web enabled and can
use generic tools for Web access.
WSDL may not describe the entire service but only the
interface and protocol bindings. The details of the
operations will be hidden under a description that uses a
specification other than WSDL.