- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 25 Apr 2005 12:13:41 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv12409
Modified Files:
wsdl20-primer.xml
Log Message:
Reviewed 6.6 and 7.9
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -C2 -d -r1.61 -r1.62
*** wsdl20-primer.xml 21 Apr 2005 17:54:18 -0000 1.61
--- wsdl20-primer.xml 25 Apr 2005 12:13:38 -0000 1.62
***************
*** 1062,1065 ****
--- 1062,1066 ----
<description xmlns="http://www.w3.org/2004/08/wsdl"
. . .
+ type="http://www.w3.org/@@@@/@@/wsdl/http"
xmlns:whttp="http://www.w3.org/@@@@/@@/wsdl/http" >
***************
*** 1070,1074 ****
<operation ref="tns:opCheckAvailability"
! whttp:location="{tCheckAvailability}" >
</binding>
--- 1071,1075 ----
<operation ref="tns:opCheckAvailability"
! whttp:location="{checkInDate}" />
</binding>
***************
*** 1085,1089 ****
</description>]]></eg>
</example>
! <div3><head>Explanation of Example</head><ednote><name>dbooth</name><date>2005-04-15</date><edtext>ToDo: Check this section. I'm not sure I got it all right, particularly regarding whttp:location. Is the first sample request URI correct? Shouldn't instance data for tCheckAvailability be in the path component? What happens if a non-leaf element type is specified, such as tCheckAvailability?</edtext></ednote><p><glist><gitem><label><code>xmlns:whttp="http://www.w3.org/@@@@/@@/wsdl/http" ></code></label><def><p>This defines the namespace prefix for elements and attributes defined by the WSDL 2.0 HTTP binding extension.</p></def></gitem><gitem><label><code>whttp:methodDefault="GET"></code></label><def><p>The default method for operations in this interface will be HTTP GET.</p></def></gitem><gitem><label><code>whttp:location="{tCheckAvailability}" ></code></label><def><p>The <code>whttp:location</code> attribute specifies a pattern for serializing input message instance data into the path compnent of the request URI. The default binding rules for HTTP specify that the default input
serialization for GET is <code>application/x-www-form-urlencoded</code>. Curly braces are used to specify the name of a schema type in the input message schema, which determines what input instance data will be inserted into the path component of the request URI. The curly brace-enclosed name will be replaced with instance data in constructing the path component. Remaining input instance data (not specified by <code>whttp:location</code>) will either be serialized into the query string portion of the URI or into the message body, as follows: if a "/" is appended to a curly brace-enclosed type name, then any remaining input message instance data will be serialized into the message body. Otherwise it will be serialized into query parameters.</p><p>Thus, in this example, each of the elements in the <code>tCheckAvailability</code> type will be serialized into
the query parameters.
--- 1086,1099 ----
</description>]]></eg>
</example>
! <div3><head>Explanation of
! Example</head><ednote><name>dbooth</name><date>2005-04-15</date><edtext>ToDo: Check this section. I'm not sure I got it all right, particularly regarding whttp:location. Is the first sample request URI correct? Shouldn't instance data for tCheckAvailability be in the path component? What happens if a non-leaf element type is specified, such as tCheckAvailability?</edtext></ednote><p><glist><gitem>
! <label><code>type="http://www.w3.org/@@@@/@@/wsdl/http"</code></label>
! <def>
! <p>
! This declares the binding as being an HTTP binding.
! </p>
! </def>
! </gitem><gitem>
! <label><code>xmlns:whttp="http://www.w3.org/@@@@/@@/wsdl/http" ></code></label><def><p>This defines the namespace prefix for elements and attributes defined by the WSDL 2.0 HTTP binding extension.</p></def></gitem><gitem><label><code>whttp:methodDefault="GET"></code></label><def><p>The default method for operations in this interface will be HTTP GET.</p></def></gitem><gitem><label><code>whttp:location="{checkInDate}" ></code></label><def><p>The <code>whttp:location</code> attribute specifies a pattern for serializing input message instance data into the path component of the request URI. The default binding rules for HTTP specify that the default input
serialization for GET is <code>application/x-www-form-urlencoded</code>. Curly braces are used to specify the name of a schema type in the input message schema, which determines what input instance data will be inserted into the path component of the request URI. The curly brace-enclosed name will be replaced with instance data in constructing the path component. Remaining input instance data (not specified by <code>whttp:location</code>) will either be serialized into the query string portion of the URI or into the message body, as follows: if a "/" is appended to a curly brace-enclosed type name, then any remaining input message instance data will be serialized into the message body. Otherwise it will be serialized into query parameters.</p><p>Thus, in this example, each of the elements in the <code>tCheckAvailability</code> type will be serialized into
the query parameters.
***************
*** 1092,1096 ****
resulting URI for would therefore be
! <code>http://greath.example.com/2004/?checkInDate=5-5-5&checkOutDate=6-6-5&roomType=foo</code>
. </p></def></gitem></glist></p><p>Here is an alternate example that serializes appends "/" to the type name in order to serialize the remaining instance data into the message body:</p><example id="example-bindings-http-path-subsset">
--- 1102,1106 ----
resulting URI for would therefore be
! <code>http://greath.example.com/2004/5-5-5?checkOutDate=6-6-5&roomType=foo</code>
. </p></def></gitem></glist></p><p>Here is an alternate example that serializes appends "/" to the type name in order to serialize the remaining instance data into the message body:</p><example id="example-bindings-http-path-subsset">
***************
*** 2139,2146 ****
<head>
Reservation Details Web Service Using HTTP Transfer</head>
! <ednote><name>dbooth</name><date>2005-04-15</date><edtext>ToDo: Check/fix this example. Shouldn't it specify what protocol to use?</edtext></ednote><eg>
<![CDATA[. . .
<binding name="reservationDetailsHTTPBinding"
! interface="tns:reservationDetailsInterface" >
<operation ref="tns:retrieve"
--- 2149,2157 ----
<head>
Reservation Details Web Service Using HTTP Transfer</head>
! <eg>
<![CDATA[. . .
<binding name="reservationDetailsHTTPBinding"
! type="http://www.w3.org/2004/08/wsdl/http"
! interface="tns:reservationDetailsInterface" >
<operation ref="tns:retrieve"
***************
*** 2160,2166 ****
<head>
Reservation List Web Service Using HTTP GET</head>
! <ednote><name>dbooth</name><date>2005-04-15</date><edtext>ToDo: Check/fix this example. Shouldn't it specify what protocol to use?</edtext></ednote><eg>
<![CDATA[. . .
<binding name="reservationListHTTPBinding"
interface="tns:reservationListInterface"
whttp:methodDefault="GET">
--- 2171,2178 ----
<head>
Reservation List Web Service Using HTTP GET</head>
! <eg>
<![CDATA[. . .
<binding name="reservationListHTTPBinding"
+ type="http://www.w3.org/2004/08/wsdl/http"
interface="tns:reservationListInterface"
whttp:methodDefault="GET">
***************
*** 2170,2180 ****
<operation ref="tns:retrieveByConfirmationNumber"
! whttp:location="/ConfirmationNumber/{confirmationNumber/}" />
<operation ref="tns:retrieveByCheckInDate"
! whttp:location="/CheckInDate/{checkInDate/}" />
<operation ref="tns:retrieveByCheckOutDate"
! whttp:location="/CheckOutDate/{checkOutDate/}" />
</binding>
. . .
--- 2182,2192 ----
<operation ref="tns:retrieveByConfirmationNumber"
! whttp:location="reservationList/ConfirmationNumber/{confirmationNumber/}" />
<operation ref="tns:retrieveByCheckInDate"
! whttp:location="reservationList/CheckInDate/{checkInDate/}" />
<operation ref="tns:retrieveByCheckOutDate"
! whttp:location="reservationList/CheckOutDate/{checkOutDate/}" />
</binding>
. . .
***************
*** 2215,2219 ****
</example><p>The WSDL service that offers this type serialized as a parameter would look like this:</p><example id="example_reservationList_HTTP_GET_single_wsdl">
<head>WSDL for Using a Single Query Type</head>
! <ednote><name>dbooth</name><date>2005-04-15</date><edtext>ToDo: Check/fix this example. Shouldn't it specify what protocol to use?</edtext></ednote><eg>
<![CDATA[. . .
<interface name="reservationListInterfaceWithQuery">
--- 2227,2231 ----
</example><p>The WSDL service that offers this type serialized as a parameter would look like this:</p><example id="example_reservationList_HTTP_GET_single_wsdl">
<head>WSDL for Using a Single Query Type</head>
! <eg>
<![CDATA[. . .
<interface name="reservationListInterfaceWithQuery">
***************
*** 2230,2238 ****
<binding name="reservationListQueryHTTPBinding"
interface="tns:reservationListInterfaceWithQuery"
whttp:methodDefault="GET">
<operation ref="tns:retrieveByReservationQuery"
! whttp:location="/{ReservationQuery}}" />
</binding>
--- 2242,2251 ----
<binding name="reservationListQueryHTTPBinding"
+ type="http://www.w3.org/2004/08/wsdl/http"
interface="tns:reservationListInterfaceWithQuery"
whttp:methodDefault="GET">
<operation ref="tns:retrieveByReservationQuery"
! whttp:location="reservationList/{ReservationQuery}}" />
</binding>
Received on Monday, 25 April 2005 12:13:47 UTC