2002/ws/desc/wsdl20 wsdl20-primer.xml,1.80,1.81

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv28629

Modified Files:
	wsdl20-primer.xml 
Log Message:
Fixed SOAP ns URI


Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.80
retrieving revision 1.81
diff -C2 -d -r1.80 -r1.81
*** wsdl20-primer.xml	3 May 2005 12:29:22 -0000	1.80
--- wsdl20-primer.xml	3 May 2005 12:34:37 -0000	1.81
***************
*** 76,80 ****
  		</langusage>
  		<revisiondesc>
! 			<p>Last Modif"Editors' copy $Date$</p>
  		</revisiondesc>
  	</header>
--- 76,80 ----
  		</langusage>
  		<revisiondesc>
! 			<p>Last Modif"Editor"Editors' copy $Date$</p>
  		</revisiondesc>
  	</header>
***************
*** 132,136 ****
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap12"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  
--- 132,136 ----
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  
***************
*** 184,188 ****
    <binding name="reservationSOAPBinding" 
  	  interface="tns:reservationInterface"
! 	  type="http://www.w3.org/2005/05/wsdl/soap12"
  	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
   
--- 184,188 ----
    <binding name="reservationSOAPBinding" 
  	  interface="tns:reservationInterface"
! 	  type="http://www.w3.org/2005/05/wsdl/soap"
  	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
   
***************
*** 366,370 ****
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap12"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    . . .
--- 366,370 ----
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    . . .
***************
*** 380,384 ****
    <binding name="reservationSOAPBinding" 
  	  interface="tns:reservationInterface"
! 	  type="http://www.w3.org/2005/05/wsdl/soap12"
  	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
--- 380,384 ----
    <binding name="reservationSOAPBinding" 
  	  interface="tns:reservationInterface"
! 	  type="http://www.w3.org/2005/05/wsdl/soap"
  	  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
***************
*** 393,397 ****
    . . .
  </description>]]></eg>
! 				</example><div3 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap12"</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>name</att> attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 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 target namespace for this WSDL 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 mechanim can be used to combine components that are defined in different WSDL target namespaces.</p></def></gitem><gitem><label><code>type="http://www.w3.org/2005/05/wsdl/soap12"</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 not defining a new operation; rather, it is referencing the
--- 393,397 ----
    . . .
  </description>]]></eg>
! 				</example><div3 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap"</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> eement.  The <att>name</att> attribute defines a name for this binding.  Each name must be unique among all  bindings in this WSDL 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 target namespace for this WSDL 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 mechanismcan be used to combine components that are defined in different WSDL target namespaces.</p></def></gitem><gitem><label><code>type="http://www.w3.org/2005/05/wsdl/soap"</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 not defining a new operation; rather, it is referencing the
***************
*** 417,421 ****
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap12"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    . . .
--- 417,421 ----
      xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc"
      xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc"
!     xmlns:wsoap= "http://www.w3.org/2005/05/wsdl/soap"
      xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    . . .
***************
*** 1131,1135 ****
  <binding name="reservationSecureSOAPBinding"
      interface="tns:reservationInterface"
!     type="http://www.w3.org/2005/05/wsdl/soap12"
      wsoap:protocol="http://bindings.example.com/SOAPBindings/secureHTTP">
    . ..
--- 1131,1135 ----
  <binding name="reservationSecureSOAPBinding"
      interface="tns:reservationInterface"
!     type="http://www.w3.org/2005/05/wsdl/soap"
      wsoap:protocol="http://bindings.example.com/SOAPBindings/secureHTTP">
    . ..
***************
*** 1479,1483 ****
  <binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
!     type="http://www.w3.org/2005/05/wsdl/soap12"
      wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
--- 1479,1483 ----
  <binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
!     type="http://www.w3.org/2005/05/wsdl/soap"
      wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
***************
*** 1690,1694 ****
  	xmlns:tns="http://greath.example.com/2004/services/reservationDetails"
  	xmlns:wdetails="http://greath.example.com/2004/schemas/reservationDetails"
! 	xmlns:wsoap="http://www.w3.org/2005/05/wsdl/soap12"
  	xmlns:xs="http://www.w3.org/2001/XMLSchema">
  
--- 1690,1694 ----
  	xmlns:tns="http://greath.example.com/2004/services/reservationDetails"
  	xmlns:wdetails="http://greath.example.com/2004/schemas/reservationDetails"
! 	xmlns:wsoap="http://www.w3.org/2005/05/wsdl/soap"
  	xmlns:xs="http://www.w3.org/2001/XMLSchema">
  
***************
*** 1730,1734 ****
  	<binding name="reservationDetailsSOAPBinding"
  		interface="tns:reservationDetailsInterface"
! 		type="http://www.w3.org/2005/05/wsdl/soap12"
  		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
--- 1730,1734 ----
  	<binding name="reservationDetailsSOAPBinding"
  		interface="tns:reservationDetailsInterface"
! 		type="http://www.w3.org/2005/05/wsdl/soap"
  		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
***************
*** 2020,2024 ****
  	xmlns:details="http://greath.example.com/2004/schemas/reservationDetails"
  	xmlns:list="http://greath.example.com/2004/schemas/reservationList"
! 	xmlns:wsoap="http://www.w3.org/2005/05/wsdl/soap12"
  	xmlns:xs="http://www.w3.org/2001/XMLSchema">
  
--- 2020,2024 ----
  	xmlns:details="http://greath.example.com/2004/schemas/reservationDetails"
  	xmlns:list="http://greath.example.com/2004/schemas/reservationList"
! 	xmlns:wsoap="http://www.w3.org/2005/05/wsdl/soap"
  	xmlns:xs="http://www.w3.org/2001/XMLSchema">
  
***************
*** 2069,2073 ****
  	<binding name="reservationListSOAPBinding"
  		interface="tns:reservationListInterface"
! 		type="http://www.w3.org/2005/05/wsdl/soap12"
  		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  
--- 2069,2073 ----
  	<binding name="reservationListSOAPBinding"
  		interface="tns:reservationListInterface"
! 		type="http://www.w3.org/2005/05/wsdl/soap"
  		wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
  

Received on Tuesday, 3 May 2005 12:34:45 UTC