- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 22 Nov 2005 21:29:25 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv4606
Modified Files:
ws-addr-wsdl.xml
Log Message:
Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model
Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -C2 -d -r1.60 -r1.61
*** ws-addr-wsdl.xml 7 Nov 2005 07:08:53 -0000 1.60
--- ws-addr-wsdl.xml 22 Nov 2005 21:29:23 -0000 1.61
***************
*** 335,340 ****
</tr>
<tr>
! <td>Yes, using another protocol or using SOAP headers with a soap:mustUnderstand
! value of "false"</td>
<td>REQUIRED</td>
<td>REQUIRED</td>
--- 335,340 ----
</tr>
<tr>
! <td>Yes, using another protocol or using SOAP headers with a
! soap:mustUnderstand value of "false"</td>
<td>REQUIRED</td>
<td>REQUIRED</td>
***************
*** 351,363 ****
</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
--- 351,360 ----
</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
***************
*** 408,411 ****
--- 405,421 ----
</binding></eg>
</example>
+ <div3>
+ <head>WSDL 2.0 Component Model Changes</head>
+ <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
+ component model:</p>
+ <ulist>
+ <item>
+ <p>A property of the binding or endpoint named {addressing required} of
+ type xs:boolean. The property value is the value of the
+ wsdl:required attribute information item on the wsaw:UsingAddressing
+ extension element, if present; otherwise "false".</p>
+ </item>
+ </ulist>
+ </div3>
</div2>
<div2>
***************
*** 468,477 ****
specify SOAPAction values for the input messages of operations. In the
absence of a wsaw:Action attribute on a WSDL input element where a
! SOAPAction value is specified, the value
! of the [action] property for the input message is
! the value of the SOAPAction specified. &wsa-soap.title;[<bibref
! ref="WSADDR-SOAP"/>] specifies restrictions on the relationship between
! the values of [action]
! and SOAPAction for SOAP 1.1 and SOAP 1.2.</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
--- 478,486 ----
specify SOAPAction values for the input messages of operations. In the
absence of a wsaw:Action attribute on a WSDL input element where a
! SOAPAction value is specified, the value of the [action] property for the
! input message is the value of the SOAPAction specified.
! &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>] specifies restrictions
! on the relationship between the values of [action] and SOAPAction for SOAP
! 1.1 and SOAP 1.2.</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
***************
*** 654,657 ****
--- 663,681 ----
</example>
</div3>
+ <div3>
+ <head>WSDL 2.0 Component Model Changes</head>
+ <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
+ component model:</p>
+ <ulist>
+ <item>
+ <p>A property of the Interface Message
+ Reference and Interface Fault components named {action}. The
+ property is of type xs:anyURI. The
+ property value is the value of the wsaw:action attribute information item, if present;
+ otherwise the default value computed following the rules from
+ section <specref ref="defactionwsdl20"/>.</p>
+ </item>
+ </ulist>
+ </div3>
<div3 id="defactionwsdl11">
<head> Default Action Pattern for WSDL 1.1</head>
***************
*** 789,793 ****
<head>Reference Parameters</head>
<p>The wsa:ReferenceParameters element (see &wsa-core.title;[<bibref
! ref="WSADDR-CORE"/>]) MAY be used as an extension child element of the
wsdl20:endpoint or wsdl11:port elements. When present, the value of the
[reference parameters] message addressing property for a message sent to an
--- 813,817 ----
<head>Reference Parameters</head>
<p>The wsa:ReferenceParameters element (see &wsa-core.title;[<bibref
! ref="WSADDR-CORE"/>]) MAY be used as an extension child element of the
wsdl20:endpoint or wsdl11:port elements. When present, the value of the
[reference parameters] message addressing property for a message sent to an
Received on Tuesday, 22 November 2005 21:29:45 UTC