wsaTestPortTypePortExplicitAction wsaTestPortTypePortExplicitAction wsaTestPortTypePortExplicitAction wsaTestPortTypePortAddressingRequired wsaTestPortTypePortAddressingRequired wsaTestPortTypePortAddressingRequired wsaTestPortTypePortSoapAction wsaTestPortTypePortAddressingRequired wsaTestPortTypePortAddressingRequired . The client sends an Anonymous Request and receives an Anonymous Response on the HTTP response.]]> IEchoString . The client sends a non-anonymous Request and receives a non-anonymous Response on a new HTTP connection.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . The client sends a Valid Anonymous ReplyTo / Non-Anonymous FaultTo Request and receives an Anonymous Response on the HTTP response.]]> IEchoString . The client sends an Invalid Anonymous ReplyTo / Non-Anonymous FaultTo Request and receives an Non-Anonymous wsa:ActionNotSupported fault on a new HTTP connection.]]> IEchoString . The client sends a Valid Non-Anonymous ReplyTo / Anonmyous FaultTo Request and receives a Non-Anonymous Response on a new HTTP connection.]]> IEchoString . The client sends an Invalid Non-Anonymous ReplyTo / Anonymous FaultTo Request and receives a wsa:ActionMismatch fault on the HTTP response.]]> IEchoString . The client sends an Anonymous Request and receives an Anonymous Response.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . The client sends a Non-Anonymous Request and receives an Non-Anonymous Response.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . The client sends an Anonymous Request and receives an Anonymous Response on the HTTP response.]]> IEchoString . The client sends a non-anonymous Request and receives a non-anonymous Response on a new HTTP connection.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . The client sends a Valid Anonymous ReplyTo / Non-Anonymous FaultTo Request and receives an Anonymous Response on the HTTP response.]]> IEchoString . The client sends an Invalid Anonymous ReplyTo / Non-Anonymous FaultTo Request and receives an Non-Anonymous wsa:ActionNotSupported fault on a new HTTP connection.]]> IEchoString . The client sends a Valid Non-Anonymous ReplyTo / Anonmyous FaultTo Request and receives a Non-Anonymous Response on a new HTTP connection.]]> IEchoString . The client sends an Invalid Non-Anonymous ReplyTo / Anonymous FaultTo Request and receives a wsa:ActionMismatch fault on the HTTP response.]]> IEchoString . The client sends an Anonymous Request and receives an Anonymous Response.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . The client sends a Non-Anonymous Request and receives an Non-Anonymous Response.]]> IEchoString . The client sends a None Request and receives an HTTP 202 Accepted response.]]> IEchoString . A client generated from a WSDL that contained the XML fragment above and that is connected to an endpoint defined by the port type above must have the highlighted input action above in its wsa:Action header. The endpoints must respond with a message that has the highlighted output action in its wsa:Action header. See the Anonymous Request and Anonymous Response messages as an example.]]> IEchoString . Since wsdl:input element’s message attribute has the same value for both operations, the request body will be the same. The endpoint will have to dispatch the request correctly based on the wsa:Action header only and respond with a message that has the right endpoint’s action and body. The first message sent by this scenario will carry action http://tempuri.org/IEchoString/Echo and expect action http://tempuri.org/IEchoString/EchoResponse in return. The second message sent by this scenario will carry action http://tempuri.org/IEchoString/EchoToInt and expect action http://tempuri.org/IEchoString/EchoToIntResponse in return.]]> IEchoString The reasoning for this scenario is identical as for scenario 2.2. The only difference is that the wsa:Action header is now inferred from the WSDL. The first message sent by this scenario will carry action http://tempuri.org/IEchoString/Echo/Echo and expect action http://tempuri.org/IEchoString/EchoResponse/EchoResponse in return. The second message sent by this scenario will carry action http://tempuri.org/IEchoString/EchoToInt/EchoToInt and expect action http://tempuri.org/IEchoString/EchoToIntResponse/EchoToIntResponse in return.]]> IEchoString http://www.w3.org/2005/08/addressing/anonymous This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest3 This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2SOAP This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2SOAP This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2 test:wsamTest2SOAP This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2 test:wsamTest2SOAP This scenario shows that the processor can successfully extract WS-Addressing Core defined values (e.g. [address]) from an EPR]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest3 test:wsamTest3 This scenario shows that the processor faults when processing an EPR which does not conform to the WS-Addressing Metadata specification. ]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2SOAP test:wsamTest2SOAP This scenario shows that the processor faults when processing an EPR which does not conform to the WS-Addressing Metadata specification. ]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2SOAP test:wsamTest2SOAP This scenario shows that the processor extracts the wsam:Metadata from conforming EPRs.]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2SOAP This scenario shows that the processor extracts the wsam:Metadata from conforming EPRs.]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2 test:wsamTest2SOAP This scenario shows that the processor extracts the wsam:Metadata from conforming EPRs.]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2 test:wsamTest2SOAP This scenario shows that the processor extracts the wsam:Metadata from conforming EPRs.]]> http://www.w3.org/2005/08/addressing/anonymous test:wsamTest2 test:wsamTest2SOAP This scenario shows that the processor extracts the wsam:Metadata from conforming EPRs.]]> ServiceInterface ServiceInterface ServiceInterface ServiceInterface ServiceInterface ServiceInterface