D:\soapui-workspace\soapui\src\wstftruetruetruehttp://www.w3.org/2006/03/addressing/ws-addr.xsd ]]>http://www.w3.org/2001/XMLSchemahttp://www.wstf.org/docs/scenarios/sc003/sc003.wsdl Note the use of distinct action values for the input and output messages of this operation. This port supports the optional use of WS-Addressing 1.0. This port supports the optional use of WS-Addressing 1.0. ]]>http://schemas.xmlsoap.org/wsdl/http://www.wstf.org/docs/scenarios/sc002/sc002.xsd ]]>http://www.w3.org/2001/XMLSchemahttp://www.soaphub.org/wstf/services/sc002http://webservice.bea.com/NotifyEcho/soap11servicehttp://ws2.withoutawire.com:9082/sc002/sc002ServiceAddrhttp://dmzrhel3.tibco.com/sc003port/wsa/wsahttp://wstf.activevos.com/active-bpel/services/sc003Servicehttp://ws2.withoutawire.com:9080/sc002/sc002Servicehttp://endpoint.jbossts.org:9090/wstf/sc003/Sc003ServiceUTF-8http://www.soaphub.org/wstf/services/sc002 ]]>UTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>UTF-8http://www.soaphub.org/wstf/services/sc002 ]]>UTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>UTF-8http://www.soaphub.org/wstf/services/sc002 ]]>http://www.w3.org/2006/03/addressing/ws-addr.xsd ]]>http://www.w3.org/2001/XMLSchemafile:/D:/soapUI-resources/sc003.wsdl Note the use of distinct action values for the input and output messages of this operation. This port supports the optional use of WS-Addressing 1.0. This port supports the optional use of WS-Addressing 1.0. ]]>http://schemas.xmlsoap.org/wsdl/file:\D:\soapUI-resources\sc002.xsd ]]>http://www.w3.org/2001/XMLSchemahttp://www.wstf.org/sc003/sc003SOAP12UTF-8http://www.wstf.org/sc003/sc003SOAP12 ]]>UTF-8http://www.wstf.org/sc003/sc003SOAP12 ? ? ]]>UTF-8http://www.wstf.org/sc003/sc003SOAP12 ]]>UTF-8http://www.wstf.org/sc003/sc003SOAP12 ? ? ]]>UTF-8http://www.wstf.org/sc003/sc003SOAP12 ]]>SEQUENTIALNotify+WSA Client sends the Notify message with WS-Addressing headers. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action is required. Succes criteria: Service responds with an HTTP 202 sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9082/sc002/sc002ServiceAddr ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Faulting Notify+WSA Client sends a faulting Notify message with WS-Addressing headers. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action is required. Succes criteria: Service responds with an HTTP 202 sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }SEQUENTIALNotify+NoMsgID Client sends Notify with wsa:Action header but no other WS-Addressing headers (not even a wsa:MessageID). Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Notify Client sends Notify with wsa:Action and wsa:MessageID headers but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyshould exclude wsa:ToUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Notify+None-ReplyTo Client sends Notify with wsa:Action, wsa:MessageID and wsa:ReplyTo set to wsa:None but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Notify+None-FaultTo Client sends Notify with wsa:Action, wsa:MessageID and wsa:FaultTo set to wsa:None but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyshould set faulTo to noneUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Notify+None-ReplyTo/FaultTo Client sends Notify with wsa:Action, wsa:MessageID and wsa:ReplyTo and wsa:FaultTo set to wsa:None but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyshould set replyTo and faultTo to noneUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Faulting Notify+NoMsgID+Anon-Reply/Fault Client sends a faulting Notify with wsa:Action and wsa:ReplyTo and wsa:FaultTo set to wsa:Anonymous but no other WS-Addressing headers. Note: there is no wsa:MessageID header. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Faulting Notify+Anon-Reply/Fault Client sends a faulting Notify with wsa:Action, wsa:MessageID and wsa:ReplyTo and wsa:FaultTo set to wsa:Anonymous but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Faulting Notify+None-Reply/Fault Client sends a faulting Notify with wsa:Action, wsa:MessageID and wsa:ReplyTo and wsa:FaultTo set to wsa:None but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://ws2.withoutawire.com:9080/sc002/sc002Service ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }MU-Faulting Notify Client sends a Notify with wsa:Action, wsa:MessageID and an additional unknown SOAP Header that is marked with the mustUnderstand attribute set to 'true'. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingNotifyUTF-8http://dmzrhel3.tibco.com/sc003port/wsa/wsa Non existing namespace and tag value! ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }SEQUENTIALSync Echo+WSA Client sends a non-faulting Echo message with WS-Addressing headers to indicate a synchronous response is expected. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action and wsa:MessageID are required. If a wsa:ReplyTo and/or wsa:FaultTo are included then they must be set to wsa:Anonymous. Success criteria: Service responds with the appropriate EchoResponse on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>truefalsetruefalsefalseASync Echo+WSA Client sends a non-faulting Echo message with WS-Addressing headers to indicate an asynchronous response is expected. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action, wsa:MessageID and wsa:ReplyTo are required. The wsa:ReplyTo must refer to an addressable endpoint. Success criteria: Service responds with the appropriate EchoResponse on a new connection to the wsa:ReplyTo EPR specified in the Echo message. On the original connection an HTTP 202 is returned. The EchoResponse message will contain the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). MessageID2c696c3f-b3cb-4593-9348-2d5907482a16sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) throw new java.lang.Exception("Error: Service responds with wrong HTTP=" + messageExchange.getResponseStatusCode());sc003SOAP11BindingEcho/testing898910000 ? ]]>declare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:Action[1]/text()http://www.wstf.org/docs/scenarios/sc002/EchoResponsefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:RelatesTo[1]/text()${Properties#MessageID}falsefalsetruefalsefalsefalseSync Faulting Echo+WSA Client sends a faulting Echo message with WS-Addressing headers to indicate a synchronous response/fault is expected. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action and wsa:MessageID are required. If the wsa:ReplyTo and/or wsa:FaultTo are included then they must be set to wsa:Anonymous. Success criteria: Service responds with a fault on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). sc003SOAP11BindingEchoUTF-8http://ws2.withoutawire.com:9082/sc002/sc002ServiceAddr ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)truefalsefalsetruefalsetruefalsefalseAsync Faulting Echo+WSA Client sends a faulting Echo message with WS-Addressing headers to indicate an asynchronous response/fault is expected. Exact list of WS-Addressing headers is implementation specific, however per the WS-Addressing spec wsa:Action, wsa:MessageID and wsa:FaultTo are required. The wsa:FaultTo must refer to an addressable endpoint. Success criteria: Service responds with a fault on a new connection to the wsa:FaultTo EPR specified in the Echo message. On the original connection an HTTP 202 is returned. The fault message will contain the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). MessageID61a7e5e2-24f3-42e6-b988-769dd294adadsc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) throw new java.lang.Exception("Service responds with HTTP=" + messageExchange.getResponseStatusCode());sc003SOAP11BindingEcho/testing898910000 ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)truefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:RelatesTo[1]/text()${Properties#MessageID}falsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:Action[1]/text()http://www.wstf.org/docs/scenarios/sc002/EchoResponsefalsefalseSEQUENTIALEcho Client sends an Echo with wsa:Action and wsa:MessageID but no other WS-Addressing headers. Success criteria: Service responds with the appropriate EchoResponse on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). sc003SOAP11BindingEchoshould exclude toUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>truefalsetruefalsefalseEcho+Anon-ReplyTo Client sends an Echo with wsa:Action, wsa:MessageID and wsa:ReplyTo set to wsa:Anonymous but no other WS-Addressing headers. Success criteria: Service responds with the appropriate EchoResponse on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action and wsa:RelatesTo at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>truefalsetruefalsefalseEcho+Anon-ReplyTo-Refs Client sends an Echo with wsa:Action, wsa:MessageID and wsa:ReplyTo set to wsa:Anonymous but no other WS-Addressing headers. The wsa:ReplyTo must include some Reference Parameters. Success criteria: Service responds with the appropriate EchoResponse on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:ReplyTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>truefalsetruetruefalsesessionId123456Echo+Anon-ReplyTo/FaultTo-Refs Client sends an Echo with wsa:Action, wsa:MessageID and wsa:ReplyTo and wsa:FaultTo set to wsa:Anonymous but no other WS-Addressing headers. The wsa:ReplyTo and wsa:FaultTo must include some Reference Parameters and the wsa:ReplyTo's Reference Parameters must differ from the wsa:FaultTo Reference Parameters. Success criteria: Service responds with the appropriate EchoResponse on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:ReplyTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>truefalsetruetruefalseFaulting-Echo+Anon-ReplyTo-Refs Client sends a faulting Echo with wsa:Action, wsa:MessageID and wsa:ReplyTo set to wsa:Anonymous but no other WS-Addressing headers. The wsa:ReplyTo must include some Reference Parameters. Success criteria: Service responds with a fault on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:ReplyTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://ws2.withoutawire.com:9082/sc002/sc002ServiceAddr ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)truefalsefalsetruefalsetruetruefalseFaulting-Echo+Anon-ReplyTo/FaultTo-Refs Client sends a faulting Echo with wsa:Action, wsa:MessageID and wsa:ReplyTo and wsa:FaultTo set to wsa:Anonymous but no other WS-Addressing headers. The wsa:ReplyTo and wsa:FaultTo must include some Reference Parameters and the wsa:ReplyTo's Reference Parameters must differ from the wsa:FaultTo Reference Parameters. Success criteria: Service responds with a fault on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:FaultTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ]]>exists( //faultcode)truefalsefalsetruefalsetruefalsetrueFaulting-Echo+Addressable-ReplyTo+Anon-FaultTo-Refs Client sends a faulting Echo with wsa:Action, wsa:MessageID, wsa:ReplyTo set to an addressable EPR, and wsa:FaultTo set to wsa:Anonymous but no other WS-Addressing headers. Success criteria: Service responds with a fault on the HTTP back-channel, with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and any request's wsa:FaultTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://dmzrhel3.tibco.com/sc003port/wsa/wsa ? ]]>exists( //faultcode)truefalsefalsetruefalsetruefalsetrueEcho+None-ReplyTo Client sends an Echo with wsa:Action, wsa:MessageID, wsa:ReplyTo set to wsa:None but no other WS-Addressing headers. Success criteria: Service responds with an HTTP 202. sc003SOAP11BindingEchoUTF-8http://webservice.bea.com/NotifyEcho/soap11service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }Echo+Addressable-ReplyTo+None-FaultTo+mU Client sends an Echo with wsa:Action, wsa:MessageID, wsa:ReplyTo set to an addressable EPR, wsa:FaultTo set to wsa:None and there is a SOAP Header with the mustUnderstand flag set to 'true' but the header is unknown to the service. Success criteria: Service responds with an mU fault on the HTTP back-channel.sc003SOAP11BindingEchoUTF-8http://wstf.activevos.com/active-bpel/services/sc003Service Non existing namespace and tag value! ? ? ]]>//faultcode[1]/text()soapenv:MustUnderstandfalsefalseEcho+Addressable-ReplyTo/FaultTo+mU Client sends an Echo with wsa:Action, wsa:MessageID, wsa:ReplyTo and wsa:FaultTo set to an addressable EPR and there is a SOAP Header with the mustUnderstand flag set to 'true' but the header is unknown to the service. Success criteria: Service responds with an mU fault on the HTTP back-channel. sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 Non existing namespace and tag value! ? ? ]]>//faultcode[1]/text()soapenv:MustUnderstandfalsefalseEcho+No-Action+Addressable-ReplyTo Client sends an Echo without a wsa:Action SOAP Header but does inlcude the wsa:MessageID SOAP Header and wsa:ReplyTo SOAP Header set to an addressable EPR. Success criteria: Service responds with WS-Addressing "Message Addressing Header Required" Fault sent to the wsa:ReplyTo EPR. sc003SOAP11BindingEchoUTF-8http://endpoint.jbossts.org:9090/wstf/sc003/Sc003Service ? ? ]]>sc003SOAP11BindingEcho/testing898910000 ? ]]>//faultcode[1]/text()wsa:MessagAddressingHeaderRequiredfalsefalseFaulting-Echo+Addressable-ReplyTo Client sends a faulting Echo with wsa:Action, wsa:MessageID and an addressable wsa:ReplyTo. Success criteria: Service responds with a fault to the wsa:ReplyTo EPR with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and any request's wsa:ReplyTo's Reference Parameters at a minimum). MessageIDe2dc8a44-10e9-4ca9-bdfb-dc602a8e7e85sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ]]>sc003SOAP11BindingEcho/testing898910000 ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)truefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //ReferenceId[1]/@wsa:IsReferenceParametertruefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:RelatesTo[1]/text()${Properties#MessageID}falsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:Action[1]/text()http://www.w3.org/2005/08/addressing/EchoResponsefalsefalseFaulting-Echo+Addressable-ReplyTo+Anon-FaultTo Client sends a faulting Echo with wsa:Action, wsa:MessageID, an addressable wsa:ReplyTo and the wsa:FaultTo EPR set to wsa:Anon. Success criteria: Service responds with a fault on the HTTP back-channel with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and any request's wsa:FaultTo's Reference Parameters at a minimum). sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)truefalsefalsetruefalsetruefalsetrueEcho+Addressable-ReplyTo Client sends an Echo with wsa:Action, wsa:MessageID and an addressable wsa:ReplyTo. Success criteria: Service responds with the appropriate EchoResponse to the wsa:ReplyTo EPR with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:ReplyTo's Reference Parameters at a minimum). MessageID6d437e33-5c0c-472a-bd17-b93623d52b6esc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>sc003SOAP11BindingEcho/testing898910000 ? ]]>declare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:Action[1]/text()http://www.wstf.org/docs/scenarios/sc002/EchoResponsefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:RelatesTo[1]/text()${Properties#MessageID}falsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //XId[1]/@wsa:IsReferenceParametertruefalsefalse//XId[1]/text()123654falsefalseEcho+mU-Headers Client sends an Echo with wsa:Action, wsa:MessageID, wsa:From, wsa:ReplyTo and wsa:FaultTo with any appropriate values. All of the headers are marked with the mustUnderstand attribute set to 'true'. Success criteria: Service responds with the appropriate EchoResponse to the wsa:ReplyTo EPR with the appropriate WS-Addressing headers (wsa:Action, wsa:RelatesTo and the request's wsa:ReplyTo's Reference Parameters at a minimum). No mU Fault must be generated. MessageID236c199e-3a67-4f81-b909-b3123b2e6dd8sc003SOAP11BindingEchoUTF-8http://www.soaphub.org/wstf/services/sc002 ? ? ]]>sc003SOAP11BindingEcho/testing898910000 ? ]]>declare namespace soapenv='http://schemas.xmlsoap.org/soap/envelope/'; exists( //soapenv:Fault)falsefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:Action[1]/text()http://www.wstf.org/docs/scenarios/sc002/EchoResponsefalsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //wsa:RelatesTo[1]/text()${Properties#MessageID}falsefalse//XId[1]/text()12falsefalsedeclare namespace wsa='http://www.w3.org/2005/08/addressing'; //XId[1]/@wsa:IsReferenceParametertruefalsefalseEcho+Unreachable-ReplyTo Client sends an Echo with wsa:Action, wsa:MessageID, and wsa:ReplyTo set to an unreachable URI. Success criteria: WS-Addressing "Destination Unreachable" fault it generated. However, where does it go? If anywhere. There are two options: 1) an HTTP 202 is returned and the fault is never seen by the client 2) the fault is returned on the HTTP back-channel (ie. wsa:FaultTo). But what if the wsa:FaultTo is unreachable as well??? sc003SOAP11BindingEchoUTF-8http://webservice.bea.com/NotifyEcho/soap11service ? ? ]]>boolean success; if ( messageExchange.getResponseStatusCode() == 200 ) success = true else if ( messageExchange.getResponseStatusCode() == 202 ) success = true else success = false; if(!success) { throw new java.lang.Exception("Wrong HTTP response code:" + messageExchange.getResponseStatusCode() + ", expected: 200 or 202"); }publicIPhttp://82.117.206.40:8989/testingsessionId123456unreachableIphttp://172.30.30.177:8989/testing