One-way message containing an Action header. Everything else is defaulted.
One-way message containing an Action header. Everything else is defaulted.
Features: core02
One-way message containing a MessageID. ReplyTo and FaultTo are defaulted.
Features: core02
One-way message containing a MessageID. ReplyTo and FaultTo are defaulted.
Features: core02
One-way message containing a ReplyTo address value of none.
Features: core02
One-way message containing a ReplyTo address value of none.
Features: core02
One-way message containing a FaultTo address value of none.
Features: core02
One-way message containing a FaultTo address value of none.
Features: core01
One-way message containing none ReplyTo and FaultTo address values.
Features: core01
One-way message containing none ReplyTo and FaultTo address values.
Features: core02
One-way message containing none ReplyTo address with Reference Parameter.
Features: core02
One-way message containing none ReplyTo address with Reference Parameter.
Features: core02
One-way message containing none ReplyTo address with a WSDL 1.1 and WSDL 2.0 documents appearing in the Metadata.
Features: core02
One-way message containing none ReplyTo address with a WSDL 1.1 and WSDL 2.0 documents appearing in the Metadata.
Features: core03
One-way message containing a ReplyTo address with an element extension and an attribute extension of the ReferenceParameters and Metadata elements.
Features: core03
One-way message containing a ReplyTo address with an element extension and an attribute extension of the ReferenceParameters and Metadata elements.
Two-way message exchange containing an Action. All other fields are defaulted. The presence of a MessageID in the first message and of the corresponding RelatesTo in the second message is tested.
Two-way message exchange containing an Action. All other fields are defaulted. The presence of a MessageID in the first message and of the corresponding RelatesTo in the second message is tested.
Two-way message exchange containing an Action, MessageID and a ReplyTo of anonymous. All other fields are defaulted.
Two-way message exchange containing an Action, MessageID and a ReplyTo of anonymous. All other fields are defaulted.
Features: core09
Two-way message exchange containing an Action and a ReplyTo with the address set to anonymous. The ReplyTo contains at least one Reference Parameter value. The reply message is returned on the HTTP response with the Reference Parameter value as a first class SOAP header.
Features: core09
Two-way message exchange containing an Action and a ReplyTo with the address set to anonymous. The ReplyTo contains at least one Reference Parameter value. The reply message is returned on the HTTP response with the Reference Parameter value as a first class SOAP header.
Two-way message exchange containing an Action. The ReplyTo and FaultTo addresses are both anonymous. The ReplyTo and FaultTo contain at least one Reference Parameter value which are different. A fault message is returned on the HTTP response with the FaultTo Reference Parameter value as a first class SOAP header.
Two-way message exchange containing an Action. The ReplyTo and FaultTo addresses are both anonymous. The ReplyTo and FaultTo contain at least one Reference Parameter value which are different. A fault message is returned on the HTTP response with the FaultTo Reference Parameter value as a first class SOAP header.
Features: core10
Two-way message exchange containing an Action and a ReplyTo address, but no FaultTo EPR. The ReplyTo address is anonymous. The ReplyTo contains at least one Reference Parameter value. A fault message is returned on the HTTP response with the ReplyTo Reference Parameter value as a first class SOAP header.
Features: core10
Two-way message exchange containing an Action and a ReplyTo address, but no FaultTo EPR. The ReplyTo address is anonymous. The ReplyTo contains at least one Reference Parameter value. A fault message is returned on the HTTP response with the ReplyTo Reference Parameter value as a first class SOAP header.
Features: core10
Two-way message exchange containing an Action, a ReplyTo EPR, and a FaultTo EPR. The ReplyTo address is not anonymous. The FaultTo address is anonymous. The FaultTo contains at least one Reference Parameter value. A fault message is returned on the HTTP response.
Two-way message exchange containing an ReplyTo EPR. The Reply-To EPR is has a value of http://www.w3.org/2005/08/addressing/none. No message is sent back.
Two-way message exchange containing an ReplyTo EPR. The Reply-To EPR is has a value of "http://www.w3.org/2005/08/addressing/none" and a role of "http://www.w3.org/2003/05/soap-envelope/role/next". No message is sent back.
Features:
A SOAP header marked with @mustUndertand="1" and a FaultTo address of none. The header isn't understood and a mustUnderstand fault is generated by the underlying SOAP processing model and sent back to the node A.
Features: soap08
Two-way message exchange containing a duplicate To header.
Features: soap08
Two-way message exchange containing a duplicate Reply-To header.
Features: soap08
Two-way message exchange containing a duplicate Fault-To header.
Features: soap08
Two-way message exchange containing a duplicate action header.
Features: soap08
Two-way message exchange containing a duplicate message ID header. The RelatesTo is in essence meaningless, hence this test being informational.
Features: soap08
Two-way message exchange containing a duplicate To header, generating a ProblemHeaderQName fault detail.
Features: soap07
Two-way message exchange containing no action header.
Two-way message exchange containing a duplicate To header and ReplyTo of none. An InvalidAddressingHeader fault should be generated, but not sent due to the ReplyTo header.
Features: soap08
Two-way message exchange containing a duplicate To header.
Features: soap08
Two-way message exchange containing a duplicate Reply-To header.
Features: soap08
Two-way message exchange containing a duplicate Fault-To header.
Features: soap08
Two-way message exchange containing a duplicate action header.
Features: soap08
Two-way message exchange containing a duplicate message ID header. RelatesTo in the reply is in essence meaningless, hence this test being informational.
Features: soap08
Two-way message exchange containing a duplicate To header, generating a ProblemHeaderQName fault detail.
Features: soap08
Two-way message exchange containing a duplicate To header, generating an InvalidCardinality subcode/subcode.
Features: soap07
Two-way message exchange containing no action header.
Two-way message exchange containing a duplicate To header and ReplyTo of none. An InvalidAddressingHeader fault should be generated, but not sent due to the ReplyTo header.
Two-way message exchange containing an Action and a ReplyTo identifying an endpoint. All other fields are defaulted.
Two-way message exchange containing an Action and a ReplyTo identifying an endpoint. All other fields are defaulted.
Two-way message exchange containing an Action, a ReplyTo identifying an endpoint, and a ReplyTo targeted to none. All other fields are defaulted.
Two-way message exchange containing an Action, a ReplyTo identifying an endpoint, and a FaultTo targeted to none. All other fields are defaulted. Intended to simulate an application fault, so ReplyTo won't be used.
Two-way message exchange containing an Action, a ReplyTo identifying an endpoint, and a FaultTo targeted to none. All other fields are defaulted. Intended to simulate an application fault, so ReplyTo won't be used.
Two-way message exchange containing an Action and a ReplyTo identifying an unreachable endpoint. All other fields are defaulted.
Two-way message exchange containing an Action and a From marked with mustUnderstand. All other fields are defaulted. It is checked that the receiver understands the message.
Two-way message exchange containing an Action and a From marked with mustUnderstand. All other fields are defaulted. It is checked that the receiver understands the message.
Generated from testcases.xml using
testcases.xsl.
$Date: 2007/07/09 20:33:20 $
Copyright © 2006 W3C ® ( MIT , ERCIM ,Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public andMember privacy statements.