W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > July to September 2007

2004/ws/addressing/testsuitewsdl/testcases testcases.xml,1.2,1.3 Overview.html,1.3,1.4

From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 16 Jul 2007 21:24:11 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1IAY39-0000H0-BO@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing/testsuitewsdl/testcases
In directory hutz:/tmp/cvs-serv1003

Modified Files:
	testcases.xml Overview.html 
Log Message:
Removed tests

Index: Overview.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/testsuitewsdl/testcases/Overview.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C 2 -d -r1.3 -r1.4
*** Overview.html	16 Jul 2007 21:12:09 -0000	1.3
--- Overview.html	16 Jul 2007 21:24:08 -0000	1.4
***************
*** 12,39 ****
  <h2>WSDL 1.1/SOAP 1.1</h2>
  <ul>
- <li><a href="#test11010">test11010</a> - request-response operation
- - UsingAddressing on binding, required=true, client send addressing
- headers</li>
- <li><a href="#test11020">test11020</a> - request-response operation
- - UsingAddressing on binding, required=true, client does not send
- addressing headers</li>
- <li><a href="#test11030">test11030</a> - request-response operation
- - UsingAddressing on port, required=true, client send addressing
- headers</li>
- <li><a href="#test11040">test11040</a> - request-response operation
- - UsingAddressing on port, required=true, client does not send
- addressing headers</li>
- <li><a href="#test11050">test11050</a> - request-response operation
- - UsingAddressing on binding, required=false, client send
- addressing headers</li>
- <li><a href="#test11060">test11060</a> - request-response operation
- - UsingAddressing on binding, required=false, client does not send
- addressing headers</li>
- <li><a href="#test11070">test11070</a> - request-response operation
- - UsingAddressing on port, required=false, client send addressing
- headers</li>
- <li><a href="#test11080">test11080</a> - request-response operation
- - UsingAddressing on port, required=false, client does not send
- addressing headers</li>
  <li><a href="#test11090">test11090</a> - request-response operation
  - explicit action</li>
--- 12,15 ----
***************
*** 170,469 ****
  Association, Multiple Operations</li>
  </ul>
- <div class="testcase cr-REQUIRED"><a name="test11010" id=
- "test11010"></a><a href="#test11010">test11010</a> -
- <strong>request-response operation - UsingAddressing on binding,
- required=true, client send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:binding and wsdl:required attribute is set to true. The
- presence of WS-A headers is tested in request and response
- message.</p>
- <p>Port: wsaTestPortTypePortAddressingRequired</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message0.xml">message</a> to B.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message1.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11020" id=
- "test11020"></a><a href="#test11020">test11020</a> -
- <strong>request-response operation - UsingAddressing on binding,
- required=true, client does not send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:binding and wsdl:required attribute is set to true. The WS-A
- headers are absent on the request message and a fault message is
- returned on the HTTP response.</p>
- <p>Port: wsaTestPortTypePortAddressingRequired</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message7.xml">message</a> to B.
- <ul>
- <li><span class=
- "xpath">count(soap11:Envelope/soap11:Header/wsa:Action) =
- 0</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message8.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://www.w3.org/2005/08/addressing/fault'</span></li>
- <li><span class=
- "xpath">soap11:Envelope/soap11:Body/soap11:Fault/faultcode/(resolve-QName(.,.)
- = xs:QName('wsa:MessageAddressingHeaderRequired'))</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11030" id=
- "test11030"></a><a href="#test11030">test11030</a> -
- <strong>request-response operation - UsingAddressing on port,
- required=true, client send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:port and wsdl:required attribute is set to true. The presence
- of WS-A headers is tested in request and response message.</p>
- <p>Port: wsaTestPortTypePortAddressingRequiredOnPort</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message0.xml">message</a> to B.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message1.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11040" id=
- "test11040"></a><a href="#test11040">test11040</a> -
- <strong>request-response operation - UsingAddressing on port,
- required=true, client does not send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:port and wsdl:required attribute is set to true. The WS-A
- headers are absent on the request message and a fault is returned
- on the HTTP response.</p>
- <p>Port: wsaTestPortTypePortAddressingRequiredOnPort</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message7.xml">message</a> to B.
- <ul>
- <li><span class=
- "xpath">count(soap11:Envelope/soap11:Header/wsa:Action) =
- 0</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message8.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://www.w3.org/2005/08/addressing/fault'</span></li>
- <li><span class=
- "xpath">soap11:Envelope/soap11:Body/soap11:Fault/faultcode/(resolve-QName(.,.)
- = xs:QName('wsa:MessageAddressingHeaderRequired'))</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11050" id=
- "test11050"></a><a href="#test11050">test11050</a> -
- <strong>request-response operation - UsingAddressing on binding,
- required=false, client send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:binding and wsdl:required attribute is set to false. The
- presence of WS-A headers is tested in request and response
- message.</p>
- <p>Port: wsaTestPortTypePortAddressingNotRequired</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message0.xml">message</a> to B.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message1.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11060" id=
- "test11060"></a><a href="#test11060">test11060</a> -
- <strong>request-response operation - UsingAddressing on binding,
- required=false, client does not send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:binding and wsdl:required attribute is set to false. The WS-A
- headers are absent on the request message. A response message is
- returned on the HTTP response. If WS-A headers are present in
- response then they must not be marked mustUnderstand=true.</p>
- <p>Port: wsaTestPortTypePortAddressingNotRequired</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message8.xml">message</a> to B.
- <ul>
- <li><span class=
- "xpath">count(soap11:Envelope/soap11:Header/wsa:Action) =
- 0</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message9.xml">message</a> to A.
- <ul>
- <li><span class=
- "xpath">(count(soap11:Envelope/soap11:Header/wsa:Action) = 0) or
- (soap11:Envelope/soap11:Header/wsa:Action !=
- 'http://www.w3.org/2005/08/addressing/fault')</span></li>
- <li><span class=
- "xpath">(count(soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand)
- = 0) or
- (soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand =
- false())</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11070" id=
- "test11070"></a><a href="#test11070">test11070</a> -
- <strong>request-response operation - UsingAddressing on port,
- required=false, client send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:port and wsdl:required attribute is set to false. The presence
- of WS-A headers is tested in request and response message.</p>
- <p>Port: wsaTestPortTypePortAddressingNotRequiredOnPort</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message0.xml">message</a> to B.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message1.xml">message</a> to A.
- <ul>
- <li><span class="xpath">soap11:Envelope/soap11:Header/wsa:Action =
- 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
- <div class="testcase cr-REQUIRED"><a name="test11080" id=
- "test11080"></a><a href="#test11080">test11080</a> -
- <strong>request-response operation - UsingAddressing on port,
- required=false, client does not send addressing headers</strong>
- (<strong>REQUIRED</strong>)
- <div class="features">
- <p>Features:</p>
- </div>
- <div class="description">
- <p class="test-description">UsingAddressing appear as child of
- wsdl:port and wsdl:required attribute is set to false. The WS-A
- headers are absent on the request message. A response message is
- returned on the HTTP response. If WS-A headers are present in
- response then they must not be marked mustUnderstand=true.</p>
- <p>Port: wsaTestPortTypePortAddressingNotRequiredOnPort</p>
- <p class="message-exchange"><a href=
- "../../testsuite/exchanges/Overview.html#SOAP11-HTTP-In-Out">SOAP11-HTTP-In-Out</a></p>
- <ol>
- <li>A sends a <a href=
- "../documents/echo/soap11/message8.xml">message</a> to B.
- <ul>
- <li><span class=
- "xpath">count(soap11:Envelope/soap11:Header/wsa:Action) =
- 0</span></li>
- </ul>
- </li>
- <li>B sends a <a href=
- "../documents/echo/soap11/message9.xml">message</a> to A.
- <ul>
- <li><span class=
- "xpath">(count(soap11:Envelope/soap11:Header/wsa:Action) = 0) or
- (soap11:Envelope/soap11:Header/wsa:Action !=
- 'http://www.w3.org/2005/08/addressing/fault')</span></li>
- <li><span class=
- "xpath">(count(soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand)
- = 0) or
- (soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand =
- false())</span></li>
- </ul>
- </li>
- </ol>
- </div>
- </div>
  <div class="testcase cr-REQUIRED"><a name="test11090" id=
  "test11090"></a><a href="#test11090">test11090</a> -
--- 146,149 ----

Index: testcases.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/testsuitewsdl/testcases/testcases.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C 2 -d -r1.2 -r1.3
*** testcases.xml	14 Jul 2007 00:04:06 -0000	1.2
--- testcases.xml	16 Jul 2007 21:24:08 -0000	1.3
***************
*** 29,226 ****
  	<ns prefix="log" uri="http://www.w3.org/2002/ws/addressing/logs/" />
  
- 	<testcase xml:id="test11010" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on binding,
- 			required=true, client send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to true.
- 							The presence of WS-A headers is tested in request and response message.]]></description>
- 		<port>wsaTestPortTypePortAddressingRequired</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message0.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message1.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11020" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on binding,
- 			required=true, client does not send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to true.
- 							The WS-A headers are absent on the request message and a fault message is returned on the HTTP response.]]></description>
- 		<port>wsaTestPortTypePortAddressingRequired</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message7.xml"
- 				name="message">
- 				<assert
- 					test="count(soap11:Envelope/soap11:Header/wsa:Action) = 0" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message8.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://www.w3.org/2005/08/addressing/fault'" />
- 				<assert
- 					test="soap11:Envelope/soap11:Body/soap11:Fault/faultcode/(resolve-QName(.,.) = xs:QName('wsa:MessageAddressingHeaderRequired'))" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11030" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on port,
- 			required=true, client send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to true.
- 							The presence of WS-A headers is tested in request and response message.]]></description>
- 		<port>wsaTestPortTypePortAddressingRequiredOnPort</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message0.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message1.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11040" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on port,
- 			required=true, client does not send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to true.
- 							The WS-A headers are absent on the request message and a fault is returned on the HTTP response.]]></description>
- 		<port>wsaTestPortTypePortAddressingRequiredOnPort</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message7.xml"
- 				name="message">
- 				<assert
- 					test="count(soap11:Envelope/soap11:Header/wsa:Action) = 0" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message8.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://www.w3.org/2005/08/addressing/fault'" />
- 				<assert
- 					test="soap11:Envelope/soap11:Body/soap11:Fault/faultcode/(resolve-QName(.,.) = xs:QName('wsa:MessageAddressingHeaderRequired'))" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11050" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on binding,
- 			required=false, client send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to false.
- 							The presence of WS-A headers is tested in request and response message.]]></description>
- 		<port>wsaTestPortTypePortAddressingNotRequired</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message0.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message1.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11060" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on binding,
- 			required=false, client does not send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to false.
- 							The WS-A headers are absent on the request message. A response message is returned on the HTTP response.
- 							If WS-A headers are present in response then they must not be marked mustUnderstand=true.]]></description>
- 		<port>wsaTestPortTypePortAddressingNotRequired</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message8.xml"
- 				name="message">
- 				<assert
- 					test="count(soap11:Envelope/soap11:Header/wsa:Action) = 0" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message9.xml"
- 				name="message">
- 				<assert
- 					test="(count(soap11:Envelope/soap11:Header/wsa:Action) = 0) or (soap11:Envelope/soap11:Header/wsa:Action != 'http://www.w3.org/2005/08/addressing/fault')" />
- 				<assert
- 					test="(count(soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand) = 0) or (soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand = false())" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11070" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on port,
- 			required=false, client send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to false.
- 							The presence of WS-A headers is tested in request and response message.]]></description>
- 		<port>wsaTestPortTypePortAddressingNotRequiredOnPort</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message0.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoRequest'" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message1.xml"
- 				name="message">
- 				<assert
- 					test="soap11:Envelope/soap11:Header/wsa:Action = 'http://example.org/wsaTestService2/wsaTestPortType/echoResponse'" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
- 	<testcase xml:id="test11080" origin="" cr="REQUIRED">
- 		<title>
- 			request-response operation - UsingAddressing on port,
- 			required=false, client does not send addressing headers
- 		</title>
- 		<description><![CDATA[UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to false.
- 							The WS-A headers are absent on the request message. A response message is returned on the HTTP response.
- 							If WS-A headers are present in response then they must not be marked mustUnderstand=true.]]></description>
- 		<port>wsaTestPortTypePortAddressingNotRequiredOnPort</port>
- 		<message-exchange type="SOAP11-HTTP-In-Out"
- 			addr-binding="soap11">
- 			<message from="A" to="B" document="echo/soap11/message8.xml"
- 				name="message">
- 				<assert
- 					test="count(soap11:Envelope/soap11:Header/wsa:Action) = 0" />
- 			</message>
- 			<message from="B" to="A" document="echo/soap11/message9.xml"
- 				name="message">
- 				<assert
- 					test="(count(soap11:Envelope/soap11:Header/wsa:Action) = 0) or (soap11:Envelope/soap11:Header/wsa:Action != 'http://www.w3.org/2005/08/addressing/fault')" />
- 				<assert
- 					test="(count(soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand) = 0) or (soap11:Envelope/soap11:Header/wsa:Action/@soap11:mustUnderstand = false())" />
- 			</message>
- 		</message-exchange>
- 	</testcase>
- 
  	<testcase xml:id="test11090" origin="" cr="REQUIRED">
  		<title>request-response operation - explicit action</title>
--- 29,32 ----
Received on Monday, 16 July 2007 21:24:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 20:09:24 UTC