W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2005

Re: WSDL is oriented client?

From: Anne Thomas Manes <atmanes@gmail.com>
Date: Fri, 5 Aug 2005 08:01:05 -0400
Message-ID: <bf414ee605080505013ee298a6@mail.gmail.com>
To: tlais <mazentlais@yahoo.fr>
Cc: noah_mendelsohn@us.ibm.com, xml-dist-app@w3.org

I think Noah's primary point is that you shouldn't think of web
services only in terms of the client/server message exchange pattern
(MEP). Web services supports many different MEPs. At its core, SOAP is
a messaging system, not an RPC system. A more accurate description of
the participating entities is sender/receiver rather than
client/server. In a peer-to-peer scenario, both/all participating
parties can play the roles of sender and receiver, so there is no
"client" versus "server".

But, I take it that your question is focused on the use of SOAP for
client/server invocations. So working with a request/response MEP

Typically, a server doesn't use a WSDL document at runtime to
interpret requests or to dispatch requests to a specific service.
Instead the server uses a deployment descriptor (WSDD) which provides
specific information for mapping the abstract WSDL interface to the
concrete implementation. Depending on the approach you take when
building the service you may start with WSDL and use it to generate
the WSDD and a skeleton for the service. Alternatively, a developer
can start with code and a WSDD and generate the WSDL.

Clients, on the other hand, pretty much always start with WSDL.
Clients may compile a WSDL document a priori and use the generated
proxy to invoke services, or they may interpret the WSDL document
dynamically at runtime.


On 8/5/05, tlais <mazentlais@yahoo.fr> wrote:
> Thank you for your response Noah. I had sent the question to
> www-ws-desc@w3.org <mailto:www-ws-desc@w3.org> but
> the message had failed, any way I'll try again.
> I still have a point.
> Supposing a server provides a "TRAVEL RESERVATION" web service. Does the
> server use the WSDL document of the "TRAVEL RESERVATION" service to send
>  and receive SOAP messages? I mean does the server interpret the WSDL
> document of
> the service provided by the server itself?
> Regards
> noah_mendelsohn@us.ibm.com wrote:
> >This mailing list is traditionally used more for SOAP-related questions
> >than for WSDL, but I'll try a quick answer:  WSDL is usable by any
> >software that wants to know in advance what is required in the content of
> >SOAP message exchanges.   Typically, it's used by software development
> >tools to aid in the preparation of code that will send or receive such
> >messages.  Whether such messaging code winds up at a client, a server, a
> >peer to peer system or whatever depends on your environment.  Many common
> >implementations are currently server to server, but there are also
> >important examples of SOAP messages being sent to and from client
> >software.  I hope this helps.
> >
> >--------------------------------------
> >Noah Mendelsohn
> >IBM Corporation
> >One Rogers Street
> >Cambridge, MA 02142
> >1-617-693-4036
> >-------------------------------------
> >
> >
> >
> >
> >Hello all,
> >
> >I'm a new member in the mailing list. I've read many documents on the XML
> >and WSDL spec, but I didn't find a response to my question. I would like
> >to
> >know if the WSDL document is client oriented. I mean Only the client
> >interprets
> >the WSDL document and the server doesn't need to purse it.
> >
> >
> >Thank you for your help
> >
> >
> >
> >
> >
Received on Friday, 5 August 2005 12:01:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:27 UTC