W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-wsdl.xml,1.61,1.62

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 08 Jan 2006 23:14:29 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1Evjk5-0004Xs-V7@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv17437

Modified Files:
	ws-addr-wsdl.xml 
Log Message:
Umit's description of the Anonymous element added; Umit added to editor list.

Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -C2 -d -r1.61 -r1.62
*** ws-addr-wsdl.xml	22 Nov 2005 21:29:23 -0000	1.61
--- ws-addr-wsdl.xml	8 Jan 2006 23:14:27 -0000	1.62
***************
*** 42,45 ****
--- 42,49 ----
                  <affiliation>Computer Associates International, Inc</affiliation>
              </author>
+             <author>
+                 <name>Ümit Yalçinalp</name>
+                 <affiliation>SAP AG </affiliation>
+             </author>
          </authlist>
          <abstract>
***************
*** 307,317 ****
              <div2>
                  <head>UsingAddressing Extension Element</head>
!                 <p>WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be
!                     used to indicate that an endpoint conforms to the WS-Addressing specification.
!                     The wsdl:required attribute MAY be used to indicate whether WS-Addressing
!                     Message Addressing Properties are required in messages received from service
!                     requesters. <specref ref="mappresence"/> outlines the requirements on messages
!                     sent from an endpoint based on the contents of any preceding input message and
!                     how the use of addressing is indicated in the WSDL.</p>
                  <table border="1" id="mappresence">
                      <caption>MAPs Present in output message</caption>
--- 311,327 ----
              <div2>
                  <head>UsingAddressing Extension Element</head>
!                 <p>
!                     WS-Addressing defines an empty global element,
!                     wsaw:UsingAddressing, that may be used to indicate
!                     that an endpoint conforms to the WS-Addressing
!                     specification.  The wsdl:required attribute MAY be
!                     used to indicate whether WS-Addressing Message
!                     Addressing Properties are required in messages
!                     received from service requesters. <specref
!                     ref="mappresence"/> outlines the requirements on
!                     messages sent from an endpoint based on the
!                     contents of any preceding input message and how
!                     the use of addressing is indicated in the WSDL.
!                 </p>
                  <table border="1" id="mappresence">
                      <caption>MAPs Present in output message</caption>
***************
*** 351,380 ****
                      </tbody>
                  </table>
!                 <p>If WS-A is engaged, use of the message addressing properties MUST be fully
!                     compliant with this specification; in particular, senders MUST use all message
!                     addressing properties mandated by the &wsa-core.title;[<bibref
!                         ref="WSADDR-CORE"/>], applicable WS-Addressing protocol bindings (e.g.
!                         &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]), and this specification,
!                     and MUST follow all applicable WS-Addressing normative requirements.</p>
!                 <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
!                     element. Alternatively, the wsaw:UsingAddressing element MAY instead be included
!                     as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
!                     indicate compliance with WS-Addressing for a specific endpoint only.</p>
!                 <p>The inclusion of the wsaw:UsingAddressing element indicates that the applicable
!                     WS-Addressing specifications are supported within the constraints of the WSDL
!                     binding being used. That is, uses of the WS-Addressing specifications that may
!                     violate or are inconsistent with the semantics of the endpoint's WSDL binding
!                     are not supported unless explicitly stated by some other mechanism.</p>
!                 <p>Specifically, when included in a SOAP binding, the wsaw:UsingAddressing marker
!                     identifies the use of Web Services Addressing 1.0 bound to SOAP as defined by
!                         &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>].</p>
!                 <p>The presence of the wsaw:UsingAddressing element in the binding or endpoint
!                     (port) components of the endpoint description does not change the semantics of
!                     the binding. E.g. in the case of the WSDL SOAP/HTTP synchronous binding for
!                     request-response operations, the presence of the wsaw:UsingAddressing element
!                     does not change the requirement that the response message be sent over the same
!                     HTTP channel over which the request was received. In this case, the wsa:replyTo
!                     header in the request MUST NOT contain an address with a value different from
!                     the anonymous URI.</p>
                  <example>
                      <head>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</head>
--- 361,394 ----
                      </tbody>
                  </table>
!                 <p>If WS-A is engaged, use of the message addressing
!                     properties MUST be fully compliant with this
!                     specification; in particular, senders MUST use all
!                     message addressing properties mandated by the
!                     &wsa-core.title;[<bibref ref="WSADDR-CORE"/>],
!                     applicable WS-Addressing protocol bindings (e.g.
!                     &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]),
!                     and this specification, and MUST follow all
!                     applicable WS-Addressing normative requirements.
!                 </p>
!                 <p>The wsaw:UsingAddressing element SHOULD appear as a
!                     child of the wsdl:binding element. Alternatively,
!                     the wsaw:UsingAddressing element MAY instead be
!                     included as a child of the wsdl20:endpoint (or
!                     wsdl11:port) when an endpoint intends to indicate
!                     compliance with WS-Addressing for a specific
!                     endpoint only.</p>
!                 <p>The inclusion of the wsaw:UsingAddressing element
!                     indicates that the applicable WS-Addressing
!                     specifications are supported within the
!                     constraints of the WSDL binding being used. This
!                     inclusion allows the usage of anonymous or
!                     non-anonymous URIs as addresses in an EPR.
!                     Specifically, when included in a SOAP binding, the
!                     wsaw:UsingAddressing marker identifies the use of
!                     Web Services Addressing 1.0 bound to SOAP as
!                     defined by &wsa-soap.title;[<bibref
!                     ref="WSADDR-SOAP"/>].The presence of this element
!                     may extend the semantics of the endpoint's WSDL
!                     binding. </p>
                  <example>
                      <head>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</head>
***************
*** 420,423 ****
--- 434,529 ----
              </div2>
              <div2>
+                 <head> Anonymous Element </head>
+                 <p>
+ 		WS-Addressing defines a wsaw:Anonymous element that
+ 		may be only be used in conjunction with
+ 		wsaw:UsingAddressing (or its equivalent wsoap:module)
+ 		element. The usage of wsaw:Anonymous element is
+ 		associated with the usage constraints specified for
+ 		wsaw:UsingAddressing element. Hence, it MUST NOT
+ 		contain the wsdl:required attribute.
+                 </p>
+                 <p>The inclusion of wsaw:Anonymous without inclusion
+                 of wsaw:UsingAddressing has no normative intent and is
+                 only informational. In other words, the inclusion of
+                 wsaw:Anonymous element in WSDL alone does not imply a
+                 requirement on clients to use Message Addressing
+                 Properties in messages it sends to the service. A
+                 client, however, MAY include Message Addressing
+                 Properties in the messages it sends, either on its own
+                 initiative or as described by other elements of the
+                 service contract, regardless of the presence or
+                 absence of wsaw:UsingAddressing element.
+                 </p>
+                 <p>The wsaw:Anonymous element MAY have three distinct
+                 values that indicate three different levels of support
+                 for handling anonymous addresses in EPRs. In the
+                 following text, the term response endpoint EPR refers
+                 to the [reply endpoint] and [fault endpoint] Message
+                 Addressing Properties collectively.
+                 </p>
+                 <ulist>
+                     <item>
+ 		        <p>"optional": This value indicates that
+ 		        a response endpoint EPR in a request message
+ 		        MAY contain an anonymous URI as an address.
+                         </p>
+                     </item>
+                     <item>
+ 		        <p>"required":This value indicates that all
+ 		        response endpoints EPRs in a request message
+ 		        MUST always use anonymous URI as an address.
+                         </p>
+                         <p>If a response endpoint EPR does not contain
+                         the anonymous URI as an address value, then a
+                         predefined InvalidAddressingHeader fault
+                         defined in Web Services Addressing 1.0 - SOAP Binding [<bibref
+                         ref="WSADDR-SOAP"/>] MUST be generated. </p>
+                     </item>
+                     <item> 
+                         <p>"prohibited":This value indicates that any
+                         response EPRs in a request message MUST NOT
+                         use anonymous URI as an address.</p>
+ 			<p>If a response endpoint EPR contains the
+ 			anonymous URI as an address value, then a
+ 			predefined InvalidAddressingHeader fault
+ 			defined in Web Services Addressing 1.0 - SOAP
+ 			Binding [<bibref ref="WSADDR-SOAP"/>] MUST be
+ 			generated. </p>
+                     </item>
+ 	       </ulist>
+                <p>This element MAY appear as a child of operation
+                element in a binding element in WSDL 1.1, or as a
+                binding operation extension element in WSDL 2.0.</p>
+                <example>
+ 	           <head> Indicating use of anonymous addresses using wsaw:Anonymous. </head>
+ 		   <eg xml:space="preserve">&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
+ &nbsp; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
+ &nbsp; &lt;wsaw:UsingAddressing wsdl:required="true" /&gt;
+ &nbsp; &lt;operation name="GetLastTradePrice"&gt;
+ &nbsp;&nbsp;&nbsp; &lt;soap:operation soapaction="http://example.com/GetLastTradePrice" /&gt;
+ &nbsp;&nbsp;&nbsp; &lt;input&gt;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;soap:body use="literal" /&gt;
+ &nbsp;&nbsp;&nbsp; &lt;/input&gt;
+ &nbsp;&nbsp;&nbsp; &lt;output&gt;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;soap:body use="literal" /&gt;
+ &nbsp;&nbsp;&nbsp; &lt;/output&gt;
+ &nbsp;&nbsp;&nbsp; &lt;wsaw:Anonymous&gt;required&lt;/wsaw:Anonymous&gt;
+ &nbsp; &lt;/operation&gt;
+ &nbsp; &lt;operation name="someOther"&gt;...&lt;/operation&gt;
+ &lt;/binding&gt;
+ </eg>
+                </example>
+                <div3>
+                    <head>WSDL 2.0 Component Model Changes</head>
+ 		   <p>Use of Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
+                    <ulist>
+ 		       <item>
+ 		           <p>A property of the binding operation component {anonymous required} of type xs:string. The property value is the value of the wsaw:Anonymous element information item, if present; otherwise "optional". </p>
+                        </item>
+                    </ulist>
+                 </div3>
+             </div2>
+             <div2>
                  <head>WSDL SOAP Module</head>
                  <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of the
***************
*** 437,441 ****
    &lt;wsoap:module uri="&nsuri;/module" required="true" /&gt;
    &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" /&gt;
    &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
  &lt;/binding&gt;</eg>
--- 543,549 ----
    &lt;wsoap:module uri="&nsuri;/module" required="true" /&gt;
    &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"&gt;
!     &lt;wsaw:Anonymous&gt;required&lt;/wsaw:Anonymous&gt;
!   &lt;/operation&gt;
    &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
  &lt;/binding&gt;</eg>
Received on Sunday, 8 January 2006 23:14:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT