Hello,
Pablo has some great work establishing a working prototype for M3. It is time
we consider a list of interesting scenarios to start adding to the framework.
Besides the currently implemented hello world scenario, I would like to propose
the following scenarios:
1-SOAP 1.2 one-way message:
* One-way message containing an Action header. Everything else
is defaulted.
* As defined in the WSDL at:
O
http://www.w3.org/2002/ws/addr/testsuite/testcases/#test1200
and
o
http://www.w3.org/2002/ws/addr/testsuite/exchanges/#SOAP12-HTTP-In-Only
2-SOAP 1.2 two-way message:
*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.
*As defined in
O
http://www.w3.org/2002/ws/addr/testsuite/testcases/#test1230
and
o
http://www.w3.org/2002/ws/addr/testsuite/exchanges/#SOAP12-HTTP-In-Out
3-SOAP 1.2 two-way message with a non-anonymous ReplyTo address
* Two-way message exchange containing an Action and a ReplyTo
identifying an endpoint. All other fields are defaulted.
* As defined in
O
http://www.w3.org/2002/ws/addr/testsuite/testcases/#test1250
and
o
http://www.w3.org/2002/ws/addr/testsuite/exchanges/#SOAP12-HTTP-In-Out-Callback
4- Mutual certificate with derived keys, sign before encrypt and encrypt
signature
* As defined in the WSDL at:
O XD-SEES
http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity11.svc?wsdl
5- RequestReply_Reliable_Anonymous_Soap12_WSAddressing10_RM11
*The client and the service establish two correlated reliable
sequences with a duplex CS/CSR handshake. The client that does not have an
address that the server can connect to at will. Instead, the server must rely
on the HTTP responses to communicate information back to the client.
*As defined in the WSDL at:
O
http://131.107.72.15/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReply.svc?wsdl
*Other variants are
O Adding MTOM in the
"RequestReply_Reliable_Addressable_Soap12_WSAddressing10_RM11_ContractUsesByteArray"
test case
Generally speaking, Microsoft endpoints are hosted at [1] with documentation
offered on WS-I site and on [2].
[1] http://131.107.72.15/endpoints/Default.aspx
[2] http://mssoapinterop.org/ilab/
Abu Obeida Bakhach
Interoperability PM | Microsoft
