W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

RE: Which operation?

From: Liu, Kevin <kevin.liu@sap.com>
Date: Tue, 15 Jun 2004 21:45:02 +0200
Message-ID: <99CA63DD941EDC4EBA897048D9B0061D0B1C118D@uspalx20a.pal.sap.corp>
To: "'Ugo Corda'" <UCorda@SeeBeyond.com>, Mark Baker <distobj@acm.org>, David Booth <dbooth@w3.org>
Cc: www-ws-desc@w3.org

Hi Ugo, Thanks for the info.  

Yes, language specific mapping to/from WSDL is necessary. But it is in the domain of JSRs (or similarly forum for other languages) which is more focusing on proxy and code skeleton generation. Even in that domain, the "contract" nature of operation name is limited -  Please note quite a few platforms, such as Weblogic and NetWeaver choose to have a "virtual interface" which allows a wsdl operation to be named differently from its corresponding method implementation. They may still be JAX-RPC compliant.

so that reaffirms what DavidB already said: how applications map a wsdl operation to a implementation and how messages are dispatched to a particular operation implementation "are outside the scope of the WSDL 2.0 language."


Best Regards,
Kevin
 

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On Behalf Of Ugo Corda
Sent: Tuesday, Jun 15, 2004 12:12 PM
To: Liu, Kevin; Mark Baker; David Booth
Cc: www-ws-desc@w3.org
Subject: RE: Which operation?



I think Mark was referring to the common practice of establishing a
close connection between the operation name and the corresponding agent
implementation. For instance, Java's JAX-RPC 1.1 says (WSDL to Java
mapping):

4.3.4 WSDL Operation
A wsdl:operation defined in a wsdl:portType maps to a Java method on the
mapped Java service endpoint interface. [...] A wsdl:operation is named
by the name attribute. The operation name maps to the name of the
corresponding method on the mapped Java service endpoint interface.

and also (Java to WSDL mapping):

5.5.3 Service Endpoint Interface
A service endpoint interface (that extends java.rmi.Remote) is mapped to
the wsdl:portType element. [...] Methods defined in a service endpoint
interface are mapped to the wsdl:operation definitions in the
corresponding wsdl:portType.

Ugo

> -----Original Message-----
> From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org] On Behalf Of Liu, Kevin
> Sent: Tuesday, June 15, 2004 11:13 AM
> To: 'Mark Baker'; David Booth
> Cc: www-ws-desc@w3.org
> Subject: RE: Which operation?
> 
> 
> 
> 
> -----Original Message-----
> From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org] On Behalf Of Mark Baker
> Sent: Monday, Jun 14, 2004 08:13 PM
> 
> >> My answer would be: That depends on the semantics of the 
> application, 
> >> and
> >> the implementation of the provider agent, which are 
> outside the scope of 
> >> the WSDL 2.0 language.
> 
> >I've heard this before, but I don't really buy it, and I don't think 
> >any WSDL developer would buy it either.  Every use of WSDL I've seen 
> >uses the wsdl:operation to define the contract.
> 
> Hi Mark,
> 
> Can you elaborate why wsdl:operation is used to define the 
> contract? To my understanding, the contract is the messages 
> to be exchanged. Operation names provides some application 
> semantics, but have no significance in the run time message. 
> 
> One might define some operation style (such as RPC style as 
> defined in part 1)  to require that the top element of a 
> message must be named same as the operation name, but the 
> "contract" is still in the message schema. 
> 
> 
> Best Regards,
> Kevin
> 
> 
Received on Tuesday, 15 June 2004 15:45:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:31 GMT