W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > October to December 2005

2004/ws/addressing ws-addr-wsdl.xml,1.53,1.54

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Oct 2005 03:16:25 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1EPAcr-0004U2-2c@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.xml 
Log Message:
Incorporated the resolution of i61.

Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -C2 -d -r1.53 -r1.54
*** ws-addr-wsdl.xml	10 Oct 2005 20:20:30 -0000	1.53
--- ws-addr-wsdl.xml	11 Oct 2005 03:16:22 -0000	1.54
***************
*** 38,41 ****
--- 38,46 ----
                  <affiliation>Sun Microsystems, Inc</affiliation>
              </author>
+             <author>
+                 <name>Tony Rogers</name>
+                 <affiliation>Computer Associates International, Inc</affiliation>
+             </author>
+             
          </authlist>
          <abstract>
***************
*** 301,312 ****
                      Addressing Properties are required in messages received from service requesters.</p>
                  <p>A wsaw:UsingAddressing element with a wsdl:required attribute whose value is
!                     "true" indicates that messages exchanged with the endpoint MUST contain
!                     WS-Addressing Message Addressing Properties. A wsaw:UsingAddressing element with
!                     a wsdl:required attribute whose value is "false" indicates that the endpoint
!                     will accept input messages with or without WS-Addressing header blocks, and MAY
!                     generate output messages containing WS-Addressing headers. If a SOAP binding is
!                     used and WS-Addressing header blocks are not present in an input message then
!                     WS-Addressing header blocks encoded in the corresponding output message MUST NOT
!                     be required to be understood using the SOAP mustUnderstand mechanism.</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
--- 306,326 ----
                      Addressing Properties are required in messages received from service requesters.</p>
                  <p>A wsaw:UsingAddressing element with a wsdl:required attribute whose value is
!                     "true" indicates that messages exchanged with the endpoint MUST have WS-A
!                     engaged (as defined by a binding of the Message Addressing Properties to a
!                     protocol). A wsaw:UsingAddressing element with a wsdl:required attribute whose
!                     value is "false" indicates that the endpoint will accept input messages with or
!                     without WS-A engaged. In the latter case, if WS-A is engaged, the 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. Such an endpoint MAY generate output messages with MAPs bound to
!                     them; however, if a message with WS-A engaged is sent to that endpoint, any
!                     subsequent messages in that exchange pattern MUST also have WS-A engaged.</p>
!                 <p>If a SOAP binding is used and WS-Addressing header blocks are not  
!                     present in an input message then WS-Addressing header blocks encoded  
!                     in the corresponding output message MUST NOT be required to be  
!                     understood using the SOAP mustUnderstand mechanism.</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
***************
*** 405,408 ****
--- 419,433 ----
                      description. The type of the attribute is xs:anyURI and it is used as an
                      extension on the WSDL input, output and fault elements.</p>
+                 <p>The inclusion of wsaw:Action without inclusion of  
+                     wsaw:UsingAddressing has no normative intent and is only  
+                     informational. In other words, the inclusion of wsaw:Action  
+                     attributes 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. Other specifications  
+                     defining the value of [action] are under no constraint to be  
+                     consistent with wsaw:Action.</p>
                  <p>For example consider the following WSDL excerpt:</p>
                  <example>
Received on Tuesday, 11 October 2005 03:16:29 GMT

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