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

RE: Issue 169: Syntax for webMethod - property or attribute?

From: David Orchard <dorchard@bea.com>
Date: Thu, 24 Jun 2004 02:37:41 -0700
Message-ID: <32D5845A745BFB429CBDBADA57CD41AF087AAC95@ussjex01.amer.bea.com>
To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, "Jonathan Marsh" <jmarsh@microsoft.com>, "Web Services Description" <www-ws-desc@w3.org>

As I've said before, I don't believe that we did close this by removing "web method".  At the F2f, I pointed this out when we were talking about removing the "web method" completely and IIRC we agreed to look at it separately.  While it is true that the SOAP binding 2 MEPS only allow GET or POST, it is not true for this in the http binding or potential other bindings.  Notice that my message does not refer to the SOAP binding.

As I argued before, the webMethod is useful to specify the generic/constrained operation at the interface operation level, not just in the binding.  Choosing a generic/constrained operation is an application designers choice and should be made available to them.  I also proposed that this "webMethod" could be used as a default for the http binding's http:method.  I proposed a "useOperationWebMethod" attribute, but in retrospect the interface operation webmethod should be the default for the http binding operation method.

I further proposed a binding simplification that would deploy all the interface operations at a given URI, which would use the webmethod.  I could update the Music example to show how this helps simplify the binding.

As a use case, Atom defines operations for interacting with various items.  One of the bindings they have is to put an "HTTP PUT" inside an "HTTP POST" when firewalls, etc. don't support PUT.  Arguably this is a new "HTTP GET+POST only" binding.   Thus the availability of the web method at the application level provides re-use for them as they can define that PUT and DELETEs are bound to POST.  The alternative is that they would have to specify a binding operation for each interface operation.

My guess is that people are going to need some time to mull this over, now that we've recovered the thread.

Cheers,
Dave


> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
> Behalf Of Sanjiva Weerawarana
> Sent: Wednesday, June 23, 2004 7:47 PM
> To: Jonathan Marsh; Web Services Description
> Subject: Re: Issue 169: Syntax for webMethod - property or attribute? 
> 
> 
> 
> That's right - we removed {web method} because that knob doesn't
> exist. IIRC we closed this issue in that process but if not it
> certainly should be.
> 
> The rules for HTTP method selection are now documented in the
> default binding rules section (2.1) of part3:
> 
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20
> -bindings.html#soap-defaults
> 
> Sanjiva.
> 
> ----- Original Message ----- 
> From: "Jonathan Marsh" <jmarsh@microsoft.com>
> To: "Web Services Description" <www-ws-desc@w3.org>
> Sent: Thursday, June 24, 2004 3:12 AM
> Subject: Issue 169: Syntax for webMethod - property or attribute?
> 
> 
> >
> > Issue 169 [1] asks whether the webMethod property should be indicted
> > using property markup or an attribute.  It's been a while since we
> > raised this issue, and as I recall we removed the {web 
> method} property
> > and syntax already [2], because when http:method is 
> specified webMethod
> > is not a controllable knob in the binding - it is a fixed 
> value.  So is
> > this issue obsolete or is there a nuance I'm missing?
> >
> > [1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x169
> > [2] 
> http://lists.w3.org/Archives/Public/www-ws-desc/2004May/0073.html
> > (issue 190 discussion and resolution)
> 
> 
Received on Thursday, 24 June 2004 05:37:44 GMT

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