We read the WSDL on the server. The WSDL defines the external binding
of the service (the service API). However, the service may be Java or
any other technology and we read the WSDL along with mapping
information in the server and bind the wsdl API to the service
implementation (whatever it may be). In fact, we do very little
different on the server and client with regards WSDL processing.
In our processing pipeline the SOAP being processed is verified against
the WSDL description and then passed to an adapter that does necessary
conversions to the target service implementation (such as binding to
Java). The fact that Java is the implementaton of a service is not
relevant in the processing of the SOAP message and identifying its
target operation. The WSDL is used for this.
Rogers, Tony wrote:
The original question related to the server, not the client.
Yes, the server COULD read the WSDL, but usually it doesn't -
the WSDL is often written to describe the server after the server has
been created, or the WSDL is created at the same time as the service.
More often, the client reads the WSDL (as you suggest in the
context of client proxies) to know what the interface is like.
It is easily argued that the WSDL exists to describe the server
for the benefit of the client. However, a server could also use the
WSDL - no argument.
Perhaps the most convincing argument for a server reading the
WSDL is when a client is implementing a call-back web service.
FYI, there are test tools that
interpret WSDL dynamically. Also, some scripting technologies read WSDL
are runtime to create a client proxy.
Rational Desktop Tools Development
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: email@example.com
The WSDL document describes the travel reservation service, from its
point of view (that is, an 'in-out' MEP is 'in' to the service, followed
by 'out' from the service).
A service developer may obtain or create a WSDL and then use it to
generate a stub of the service, but it is also common that the service
is developed first, and then WSDL generated describing that service.
There is no tight run-time linkage between WSDL and the service. The
WSDL could even be provided by a third party, without the knowledge of
Probably the most important use of WSDL though will be for generating
code for clients that wish to connect to the service.
Hope this helps.
> -----Original Message-----
> From: firstname.lastname@example.org
> On Behalf Of tlais
> Sent: Friday, August 05, 2005 1:58 AM
> To: email@example.com
> Subject: question-WSDL
> Hello all,
> I'm a new member in the mailing list. I've read many documents on
> and WSDL spec, but I didn't find a response to my question.
> Supposing a server provides a "TRAVEL RESERVATION" web service.
> server use the WSDL document of the "TRAVEL RESERVATION" service to
> and receive SOAP messages? I mean does the server interpret the
> document of the service provided by the server itself?