W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > October 2006

2002/ws/desc/wsdl20 wsdl20-primer.xml,1.147,1.148 wsdl20-primer.html,1.160,1.161 wsdl20-soap11-binding.html,1.9,1.10 entities.dtd,1.39,1.40

From: Jonathan Marsh via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 20 Oct 2006 22:18:19 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1Gb2h2-0001je-0Q@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv5710/wsdl20

Modified Files:
	wsdl20-primer.xml wsdl20-primer.html 
	wsdl20-soap11-binding.html entities.dtd 
Log Message:
CR077 implementation in primer, entities.dtd, and soap11-binding.

Index: entities.dtd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/entities.dtd,v
retrieving revision 1.39
retrieving revision 1.40
diff -C 2 -d -r1.39 -r1.40
*** entities.dtd	23 Mar 2006 13:07:32 -0000	1.39
--- entities.dtd	20 Oct 2006 22:18:17 -0000	1.40
***************
*** 61,65 ****
     "http://www.w3.org/&draft.year;/&draft.mm;/soap11">
  <!ENTITY soap11-http-uri
!    "&soap11-prefix-uri;/bindings/HTTP">
  <!ENTITY soap11-request-response-mep-uri
     "&soap11-prefix-uri;/mep/request-response">
--- 61,65 ----
     "http://www.w3.org/&draft.year;/&draft.mm;/soap11">
  <!ENTITY soap11-http-uri
!    "&soap11-prefix-uri;/bindings/HTTP/">
  <!ENTITY soap11-request-response-mep-uri
     "&soap11-prefix-uri;/mep/request-response">

Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.147
retrieving revision 1.148
diff -C 2 -d -r1.147 -r1.148
*** wsdl20-primer.xml	20 Oct 2006 21:47:10 -0000	1.147
--- wsdl20-primer.xml	20 Oct 2006 22:18:16 -0000	1.148
***************
*** 209,213 ****
  	  interface="tns:reservationInterface"
  	  ]]>type="&wsdl-soap-ns;"<![CDATA[
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
   
      <fault ref="tns:invalidDataFault" 
--- 209,213 ----
  	  interface="tns:reservationInterface"
  	  ]]>type="&wsdl-soap-ns;"<![CDATA[
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
   
      <fault ref="tns:invalidDataFault" 
***************
*** 416,420 ****
  	  interface="tns:reservationInterface"
  	  ]]>type="&wsdl-soap-ns;"<![CDATA[
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
      <operation ref="tns:opCheckAvailability" 
--- 416,420 ----
  	  interface="tns:reservationInterface"
  	  ]]>type="&wsdl-soap-ns;"<![CDATA[
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
      <operation ref="tns:opCheckAvailability" 
***************
*** 428,432 ****
    . . .
  </description>]]></eg>
! 				</example><div4 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "&wsdl-soap-ns;"</code></label><def><p>We've added two more namespace declarations.  This one is the namespace for the SOAP 1.2 binding extension that is defined in WSDL 2.0 Part 3 <bibref ref="SOAP12-PART1"/>.   Elements and attributes prefixed with  <code>wsoap:</code>  are constructs defined there.  </p></def></gitem><gitem><label><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></label><def><p>This namespace is defined by the SOAP 1.2 specification itself.  The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts.  Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></def></gitem><gitem><label><code>&lt;binding name="reservationSOAPBinding"</code></label><def><p>Bindings are declared directly inside the <code>description</code> element.  The <att>nam</att> attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 2.0 target namespace, and will be used later when we define a service endpoint that references this binding.  WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></def></gitem><gitem><label><code>interface="tns:reservationInterface"</code></label><def><p>This is the name of the interface whose message format and transmission protocols we are specifying.  As discussed in <specref ref="more-bindings"/>, a reusable binding can be defined by omitting the <att>interface</att> attribute.  Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL 2.0 target namespace for this WSDL 2.0 document.  In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <specref ref="adv-import-and-authoring"/>  we will see how WSDL 2.0's import mechanism can be ued to combine components that are defined in different WSDL 2.0 target namespaces.</p></def></gitem><gitem><label><code>type="&wsdl-soap-ns;"</code></label><def><p>This specifies what kind of concrete message format to use, in this case SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></label><def><p>This attribute is specific to WSDL 2.0's SOAP binding extension (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP.  </p></def></gitem><gitem><label><code>&lt;operation ref="tns:opCheckAvailability"</code></label><def>
  	<p>
  		This is not defining a new operation; rather, it is referencing the
--- 428,432 ----
    . . .
  </description>]]></eg>
! 				</example><div4 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "&wsdl-soap-ns;"</code></label><def><p>We've added two more namespace declarations.  This one is the namespace for the SOAP 1.2 binding extension that is defined in WSDL 2.0 Part 3 <bibref ref="SOAP12-PART1"/>.   Elements and attributes prefixed with  <code>wsoap:</code>  are constructs defined there.  </p></def></gitem><gitem><label><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></label><def><p>This namespace is defined by the SOAP 1.2 specification itself.  The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts.  Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></def></gitem><gitem><label><code>&lt;binding name="reservationSOAPBinding"</code></label><def><p>Bindings are declared directly inside the <code>description</code> element.  The <att>nam</att> attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 2.0 target namespace, and will be used later when we define a service endpoint that references this binding.  WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></def></gitem><gitem><label><code>interface="tns:reservationInterface"</code></label><def><p>This is the name of the interface whose message format and transmission protocols we are specifying.  As discussed in <specref ref="more-bindings"/>, a reusable binding can be defined by omitting the <att>interface</att> attribute.  Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL 2.0 target namespace for this WSDL 2.0 document.  In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <specref ref="adv-import-and-authoring"/>  we will see how WSDL 2.0's import mechanism can be ued to combine components that are defined in different WSDL 2.0 target namespaces.</p></def></gitem><gitem><label><code>type="&wsdl-soap-ns;"</code></label><def><p>This specifies what kind of concrete message format to use, in this case SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"</code></label><def><p>This attribute is specific to WSDL 2.0's SOAP binding extension (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP.  </p></def></gitem><gitem><label><code>&lt;operation ref="tns:opCheckAvailability"</code></label><def>
  	<p>
  		This is not defining a new operation; rather, it is referencing the
***************
*** 1319,1323 ****
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
      <operation ref="tns:opCheckAvailability" 
--- 1319,1323 ----
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
      <operation ref="tns:opCheckAvailability" 
***************
*** 1365,1369 ****
  
  
! 			<div4 id="more-bindings-soap-example-explanation"><head>Explanation of Example</head><p>Most lines in this example is the same as previously explained in <specref ref="basics-binding"/>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.<glist><gitem><label><code>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</code></label><def><p>This is the namespace for terms defined within the SOAP 1.1 specification <bibref ref="SOAP11"/>.</p></def></gitem><gitem><label><code>&lt;binding...wsoap:version="1.1"</code></label><def><p>This line indicates that this binding uses SOAP 1.1 <bibref ref="WSDL-SOAP11"/>, rather than SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP"&gt;</code></label><def><p>This line specifies that HTTP should be used as the underlying transmission protocol. See  also  <specref ref="adv-get-vs-post"/>.</p></def></gitem>
  			
  <gitem><label><code>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></label><def><p>Note that <code>wsoap:mep</code> is not applicable to SOAP 1.1 binding. </p></def></gitem>
--- 1365,1369 ----
  
  
! 			<div4 id="more-bindings-soap-example-explanation"><head>Explanation of Example</head><p>Most lines in this example is the same as previously explained in <specref ref="basics-binding"/>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.<glist><gitem><label><code>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</code></label><def><p>This is the namespace for terms defined within the SOAP 1.1 specification <bibref ref="SOAP11"/>.</p></def></gitem><gitem><label><code>&lt;binding...wsoap:version="1.1"</code></label><def><p>This line indicates that this binding uses SOAP 1.1 <bibref ref="WSDL-SOAP11"/>, rather than SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP/"&gt;</code></label><def><p>This line specifies that HTTP should be used as the underlying transmission protocol. See  also  <specref ref="adv-get-vs-post"/>.</p></def></gitem>
  			
  <gitem><label><code>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></label><def><p>Note that <code>wsoap:mep</code> is not applicable to SOAP 1.1 binding. </p></def></gitem>
***************
*** 1446,1450 ****
  				<ulist>
  				
! 				<item><p>If the WSDL 2.0 SOAP binding extension is used (<specref ref="more-bindings-soap"/>), with HTTP as the underlying transport protocol, then GET may be specified by setting:<glist><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></label><def><p>on the <code>binding</code> element (to indicate the use of HTTP as the underlying protocol); and</p></def></gitem><gitem><label><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></label><def><p>on the binding <code>operation</code> element, which causes GET to be used by default.</p></def></gitem></glist> </p></item>
  				<item><p>If the WSDL 2.0 HTTP binding extension is used directly (<specref ref="more-bindings-http"/>), GET may be specified by setting either:<glist><gitem><label><code>whttp:methodDefault="GET"</code></label><def><p>on the <code>binding</code> element; or</p></def></gitem><gitem><label><code>whttp:method="GET"</code></label><def><p>on the binding <code>operation</code> element, which overrides <code>whttp:methodDefault</code> if set on the <code>binding</code> element; or </p></def></gitem>
  				<gitem><label><code>wsdlx:safe="true" </code></label><def><p> on the bound <code>interface operation </code>.  When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></def>
--- 1446,1450 ----
  				<ulist>
  				
! 				<item><p>If the WSDL 2.0 SOAP binding extension is used (<specref ref="more-bindings-soap"/>), with HTTP as the underlying transport protocol, then GET may be specified by setting:<glist><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"</code></label><def><p>on the <code>binding</code> element (to indicate the use of HTTP as the underlying protocol); and</p></def></gitem><gitem><label><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></label><def><p>on the binding <code>operation</code> element, which causes GET to be used by default.</p></def></gitem></glist> </p></item>
  				<item><p>If the WSDL 2.0 HTTP binding extension is used directly (<specref ref="more-bindings-http"/>), GET may be specified by setting either:<glist><gitem><label><code>whttp:methodDefault="GET"</code></label><def><p>on the <code>binding</code> element; or</p></def></gitem><gitem><label><code>whttp:method="GET"</code></label><def><p>on the binding <code>operation</code> element, which overrides <code>whttp:methodDefault</code> if set on the <code>binding</code> element; or </p></def></gitem>
  				<gitem><label><code>wsdlx:safe="true" </code></label><def><p> on the bound <code>interface operation </code>.  When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></def>
***************
*** 2533,2537 ****
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
   <operation ref="tns:opCheckAvailability" 
--- 2533,2537 ----
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
   <operation ref="tns:opCheckAvailability" 
***************
*** 2821,2825 ****
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
      <operation ref="tns:opCheckAvailability">
--- 2821,2825 ----
      interface="tns:reservationInterface"
      ]]>type="&wsdl-soap-ns;"<![CDATA[
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
      <operation ref="tns:opCheckAvailability">
***************
*** 2928,2932 ****
          interface="tns:reservationInterface"
          ]]>type="&wsdl-soap-ns;"<![CDATA[
!         wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
      <operation ref="tns:makeReservation"
  	wsoap:action="tns:makeReservationV2"/>
--- 2928,2932 ----
          interface="tns:reservationInterface"
          ]]>type="&wsdl-soap-ns;"<![CDATA[
!         wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
      <operation ref="tns:makeReservation"
  	wsoap:action="tns:makeReservationV2"/>
***************
*** 3117,3121 ****
  		interface="tns:reservationDetailsInterface"]]>
  		type="&wsdl-soap-ns;"<![CDATA[
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
  		<operation ref="tns:retrieve"
--- 3117,3121 ----
  		interface="tns:reservationDetailsInterface"]]>
  		type="&wsdl-soap-ns;"<![CDATA[
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
  		<operation ref="tns:retrieve"
***************
*** 3367,3371 ****
  		interface="tns:reservationListInterface"]]>
  		type="&wsdl-soap-ns;"<![CDATA[
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
  		<operation ref="tns:retrieve"
--- 3367,3371 ----
  		interface="tns:reservationListInterface"]]>
  		type="&wsdl-soap-ns;"<![CDATA[
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
  
  		<operation ref="tns:retrieve"

Index: wsdl20-soap11-binding.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-soap11-binding.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -C 2 -d -r1.9 -r1.10
*** wsdl20-soap11-binding.html	27 Feb 2006 14:22:29 -0000	1.9
--- wsdl20-soap11-binding.html	20 Oct 2006 22:18:17 -0000	1.10
***************
*** 1,15 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
!     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
! <head>
! <meta name="generator" content=
! "HTML Tidy for Mac OS X (vers 1st December 2004), see www.w3.org" />
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Description Language (WSDL) Version 2.0 SOAP
! 1.1 Binding</title>
[...1066 lines suppressed...]
! 						<td rowspan="1" colspan="1">Changed title from SOAP 11 to SOAP 1.1</td>
! 					</tr>
! 					<tr>
! 						<td rowspan="1" colspan="1">20041129</td>
! 						<td rowspan="1" colspan="1">AV</td>
! 						<td rowspan="1" colspan="1">Incorporated WG <a href="http://lists.w3.org/Archives/Public/www-ws-desc/2004Nov/0040.html">resolutions
!                 from the webMethods F2F, Nov 2004</a>
! 						</td>
! 					</tr>
! 					<tr>
! 						<td rowspan="1" colspan="1">20040826</td>
! 						<td rowspan="1" colspan="1">AV</td>
! 						<td rowspan="1" colspan="1">Created the first draft</td>
! 					</tr>
! 				</tbody>
! 			</table><br>
! 		</div>
! 	</div>
! </body></html>
\ No newline at end of file

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.160
retrieving revision 1.161
diff -C 2 -d -r1.160 -r1.161
*** wsdl20-primer.html	20 Oct 2006 21:47:10 -0000	1.160
--- wsdl20-primer.html	20 Oct 2006 22:18:16 -0000	1.161
***************
*** 240,244 ****
  	  interface="tns:reservationInterface"
  	  type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
   
      &lt;fault ref="tns:invalidDataFault" 
--- 240,244 ----
  	  interface="tns:reservationInterface"
  	  type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
   
      &lt;fault ref="tns:invalidDataFault" 
***************
*** 454,458 ****
  	  interface="tns:reservationInterface"
  	  type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
      &lt;operation ref="tns:opCheckAvailability" 
--- 454,458 ----
  	  interface="tns:reservationInterface"
  	  type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
      &lt;operation ref="tns:opCheckAvailability" 
***************
*** 467,471 ****
  &lt;/description&gt;</pre></div>
  				</div><div class="div4">
! <h5><a name="example-initial-binding-explanation"></a>2.1.5.1 Explanation of Example</h5><dl><dt class="label"><code>xmlns:wsoap= "http://www.w3.org/@@@@/@@/wsdl/soap"</code></dt><dd><p>We've added two more namespace declarations.  This one is the namespace for the SOAP 1.2 binding extension that is defined in WSDL 2.0 Part 3 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].   Elements and attributes prefixed with  <code>wsoap:</code>  are constructs defined there.  </p></dd><dt class="label"><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></dt><dd><p>This namespace is defined by the SOAP 1.2 specification itself.  The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts.  Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></dd><dt class="label"><code>&lt;binding name="reservationSOAPBinding"</code></dt><dd><p>Bindings are declared directly inside the <coe>description</code> element.  The <code>name</code>  attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 2.0 target namespace, and will be used later when we define a service endpoint that references this binding.  WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></dd><dt class="label"><code>interface="tns:reservationInterface"</code></dt><dd><p>This is the name of the interface whose message format and transmission protocols we are specifying.  As discussed in <a href="#more-bindings"><b>2.5 More on Bindings</b></a>, a reusable binding can be defined by omitting the <code>interface</code>  attribute.  Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL 2.0 target namespace for this WSDL 2.0 document.  In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <a href="#adv-import-and-autoring"><b>3.1 Importing WSDL</b></a>  we will see how WSDL 2.0's import mechanism can be used to combine components that are defined in different WSDL 2.0 target namespaces.</p></dd><dt class="label"><code>type="http://www.w3.org/@@@@/@@/wsdl/soap"</code></dt><dd><p>This specifies what kind of concrete message format to use, in this case SOAP 1.2.</p></dd><dt class="label"><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></dt><dd><p>This attribute is specific to WSDL 2.0's SOAP binding extension (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP.  </p></dd><dt class="label"><code>&lt;operation ref="tns:opCheckAvailability"</code></dt><dd>
  	<p>
  		This is not defining a new operation; rather, it is referencing the
--- 467,471 ----
  &lt;/description&gt;</pre></div>
  				</div><div class="div4">
! <h5><a name="example-initial-binding-explanation"></a>2.1.5.1 Explanation of Example</h5><dl><dt class="label"><code>xmlns:wsoap= "http://www.w3.org/@@@@/@@/wsdl/soap"</code></dt><dd><p>We've added two more namespace declarations.  This one is the namespace for the SOAP 1.2 binding extension that is defined in WSDL 2.0 Part 3 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].   Elements and attributes prefixed with  <code>wsoap:</code>  are constructs defined there.  </p></dd><dt class="label"><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></dt><dd><p>This namespace is defined by the SOAP 1.2 specification itself.  The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts.  Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></dd><dt class="label"><code>&lt;binding name="reservationSOAPBinding"</code></dt><dd><p>Bindings are declared directly inside the <coe>description</code> element.  The <code>name</code>  attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 2.0 target namespace, and will be used later when we define a service endpoint that references this binding.  WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></dd><dt class="label"><code>interface="tns:reservationInterface"</code></dt><dd><p>This is the name of the interface whose message format and transmission protocols we are specifying.  As discussed in <a href="#more-bindings"><b>2.5 More on Bindings</b></a>, a reusable binding can be defined by omitting the <code>interface</code>  attribute.  Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL 2.0 target namespace for this WSDL 2.0 document.  In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <a href="#adv-import-and-autoring"><b>3.1 Importing WSDL</b></a>  we will see how WSDL 2.0's import mechanism can be used to combine components that are defined in different WSDL 2.0 target namespaces.</p></dd><dt class="label"><code>type="http://www.w3.org/@@@@/@@/wsdl/soap"</code></dt><dd><p>This specifies what kind of concrete message format to use, in this case SOAP 1.2.</p></dd><dt class="label"><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"</code></dt><dd><p>This attribute is specific to WSDL 2.0's SOAP binding extension (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP.  </p></dd><dt class="label"><code>&lt;operation ref="tns:opCheckAvailability"</code></dt><dd>
  	<p>
  		This is not defining a new operation; rather, it is referencing the
***************
*** 1387,1391 ****
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
      &lt;operation ref="tns:opCheckAvailability" 
--- 1387,1391 ----
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
      &lt;operation ref="tns:opCheckAvailability" 
***************
*** 1402,1406 ****
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
      wsoap:version="1.1"
!     wsoap:protocol="http://www.w3.org/@@@@/@@/soap11/bindings/HTTP"&gt;
    
      &lt;operation ref="tns:opCheckAvailability"/&gt;
--- 1402,1406 ----
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
      wsoap:version="1.1"
!     wsoap:protocol="http://www.w3.org/@@@@/@@/soap11/bindings/HTTP/"&gt;
    
      &lt;operation ref="tns:opCheckAvailability"/&gt;
***************
*** 1434,1438 ****
  
  			<div class="div4">
! <h5><a name="more-bindings-soap-example-explanation"></a>2.5.5.1 Explanation of Example</h5><p>Most lines in this example is the same as previously explained in <a href="#basics-binding"><b>2.1.5 Defining a Binding</b></a>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.</p><dl><dt class="label"><code>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</code></dt><dd><p>This is the namespace for terms defined within the SOAP 1.1 specification [<cite><a href="#SOAP11">SOAP 1.1</a></cite>].</p></dd><dt class="label"><code>&lt;binding...wsoap:version="1.1"</code></dt><dd><p>This line indicates that this binding uses SOAP 1.1 [<cite><a href="#WSDL-SOAP11">WSDL 2.0 SOAP 1.1 Binding</a></cite>], rather than SOAP 1.2.</p></dd><dt class="label"><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP"&gt;</code></dt><dd><p>This line specifies that HTTP should be used as the underlying transmission protocol. See  also  <a href="#adv-et-vs-post"><b>2.5.7 HTTP GET Versus POST: Which to Use?</b></a>.</p></dd>
  			
  <dt class="label"><code>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></dt><dd><p>Note that <code>wsoap:mep</code> is not applicable to SOAP 1.1 binding. </p></dd>
--- 1434,1438 ----
  
  			<div class="div4">
! <h5><a name="more-bindings-soap-example-explanation"></a>2.5.5.1 Explanation of Example</h5><p>Most lines in this example is the same as previously explained in <a href="#basics-binding"><b>2.1.5 Defining a Binding</b></a>, so we'll only point out lines that are demonstrating something new for SOAP 1.1 binding.</p><dl><dt class="label"><code>&lt;description ... xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"&gt;</code></dt><dd><p>This is the namespace for terms defined within the SOAP 1.1 specification [<cite><a href="#SOAP11">SOAP 1.1</a></cite>].</p></dd><dt class="label"><code>&lt;binding...wsoap:version="1.1"</code></dt><dd><p>This line indicates that this binding uses SOAP 1.1 [<cite><a href="#WSDL-SOAP11">WSDL 2.0 SOAP 1.1 Binding</a></cite>], rather than SOAP 1.2.</p></dd><dt class="label"><code>wsoap:protocol="http://www.w3.org/2005/05/soap11/bindings/HTTP/"&gt;</code></dt><dd><p>This line specifies that HTTP should be used as the underlying transmission protocol. See  also  <a href="#advget-vs-post"><b>2.5.7 HTTP GET Versus POST: Which to Use?</b></a>.</p></dd>
  			
  <dt class="label"><code>&lt;operation ref="tns:opCheckAvailability"/&gt;</code></dt><dd><p>Note that <code>wsoap:mep</code> is not applicable to SOAP 1.1 binding. </p></dd>
***************
*** 1518,1522 ****
  				<ul>
  				
! 				<li><p>If the WSDL 2.0 SOAP binding extension is used (<a href="#more-bindings-soap"><b>2.5.5 The SOAP Binding Extension</b></a>), with HTTP as the underlying transport protocol, then GET may be specified by setting:</p><dl><dt class="label"><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></dt><dd><p>on the <code>binding</code> element (to indicate the use of HTTP as the underlying protocol); and</p></dd><dt class="label"><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></dt><dd><p>on the binding <code>operation</code> element, which causes GET to be used by default.</p></dd></dl><p> </p></li>
  				<li><p>If the WSDL 2.0 HTTP binding extension is used directly (<a href="#more-bindings-http"><b>2.5.6 The HTTP Binding Extension</b></a>), GET may be specified by setting either:</p><dl><dt class="label"><code>whttp:methodDefault="GET"</code></dt><dd><p>on the <code>binding</code> element; or</p></dd><dt class="label"><code>whttp:method="GET"</code></dt><dd><p>on the binding <code>operation</code> element, which overrides <code>whttp:methodDefault</code> if set on the <code>binding</code> element; or </p></dd>
  				<dt class="label"><code>wsdlx:safe="true" </code></dt><dd><p> on the bound <code>interface operation </code>.  When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></dd>
--- 1518,1522 ----
  				<ul>
  				
! 				<li><p>If the WSDL 2.0 SOAP binding extension is used (<a href="#more-bindings-soap"><b>2.5.5 The SOAP Binding Extension</b></a>), with HTTP as the underlying transport protocol, then GET may be specified by setting:</p><dl><dt class="label"><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"</code></dt><dd><p>on the <code>binding</code> element (to indicate the use of HTTP as the underlying protocol); and</p></dd><dt class="label"><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></dt><dd><p>on the binding <code>operation</code> element, which causes GET to be used by default.</p></dd></dl><p> </p></li>
  				<li><p>If the WSDL 2.0 HTTP binding extension is used directly (<a href="#more-bindings-http"><b>2.5.6 The HTTP Binding Extension</b></a>), GET may be specified by setting either:</p><dl><dt class="label"><code>whttp:methodDefault="GET"</code></dt><dd><p>on the <code>binding</code> element; or</p></dd><dt class="label"><code>whttp:method="GET"</code></dt><dd><p>on the binding <code>operation</code> element, which overrides <code>whttp:methodDefault</code> if set on the <code>binding</code> element; or </p></dd>
  				<dt class="label"><code>wsdlx:safe="true" </code></dt><dd><p> on the bound <code>interface operation </code>.  When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></dd>
***************
*** 2619,2623 ****
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
   &lt;operation ref="tns:opCheckAvailability" 
--- 2619,2623 ----
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
   &lt;operation ref="tns:opCheckAvailability" 
***************
*** 2908,2912 ****
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
      &lt;operation ref="tns:opCheckAvailability"&gt;
--- 2908,2912 ----
      interface="tns:reservationInterface"
      type="http://www.w3.org/@@@@/@@/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
      &lt;operation ref="tns:opCheckAvailability"&gt;
***************
*** 3020,3024 ****
          interface="tns:reservationInterface"
          type="http://www.w3.org/@@@@/@@/wsdl/soap"
!         wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
      &lt;operation ref="tns:makeReservation"
  	wsoap:action="tns:makeReservationV2"/&gt;
--- 3020,3024 ----
          interface="tns:reservationInterface"
          type="http://www.w3.org/@@@@/@@/wsdl/soap"
!         wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
      &lt;operation ref="tns:makeReservation"
  	wsoap:action="tns:makeReservationV2"/&gt;
***************
*** 3212,3216 ****
  		interface="tns:reservationDetailsInterface"
  		type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
  		&lt;operation ref="tns:retrieve"
--- 3212,3216 ----
  		interface="tns:reservationDetailsInterface"
  		type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
  		&lt;operation ref="tns:retrieve"
***************
*** 3463,3467 ****
  		interface="tns:reservationListInterface"
  		type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
  
  		&lt;operation ref="tns:retrieve"
--- 3463,3467 ----
  		interface="tns:reservationListInterface"
  		type="http://www.w3.org/@@@@/@@/wsdl/soap"
! 		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"&gt;
  
  		&lt;operation ref="tns:retrieve"
Received on Friday, 20 October 2006 22:18:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:20 UTC