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

Additional HTTP and safety primer example and text

From: David Orchard <dorchard@bea.com>
Date: Wed, 15 Jun 2005 21:59:27 -0700
Message-ID: <32D5845A745BFB429CBDBADA57CD41AF1066BB08@ussjex01.amer.bea.com>
To: "WS-Description WG" <www-ws-desc@w3.org>
Section 2.4 and 5.1 example should change safe to wsdlx:safe

 

I suggest 5.4.1 needs some text to describe how wsdlx:safe can be used.
My suggestion: The wsdlx:safe attribute may be used in bindings.  The
HTTP binding uses a "true" setting of wsdlx:safe to indicate that HTTP
GET is the operation, simplifying the HTTP Binding.

 

Example 6.2 needs type="http://www.w3.org/2005/05/wsdl/http" in the
binding.

 

Addition to 6.7

 

wsdlx:safe="true"

on the interface operation element.  The HTTP Binding will set the
method to GET if wsdlx:safe="true"

 

I suggest a new section 6.8

 

6.8 Safety and the HTTP Binding

In the GreatH interface definition shown in example 2.4, the wsdlx:safe
attribute = "true".  The HTTP binding will use this value to set the
http method to GET, meaning that methodDefault on binding or method on
binding operation do not need to be set for HTTP GET.  The HTTP Binding
can be simplified to:

 

<binding name="reservationHTTPBinding"

      interface="tns:reservationInterface"

      type="http://www.w3.org/2005/05/wsdl/http" >

 

    <operation ref="tns:opCheckAvailability"

        whttp:location="{checkInDate}"/>

  </binding>

 

The binding operation has used the wsdlx:safe attribute to generate the
HTTP GET operation.

 
Received on Thursday, 16 June 2005 05:00:32 GMT

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