W3C home > Mailing lists > Public > public-ws-addressing@w3.org > September 2005

enumerated list of concrete message exchanges

From: <paul.downey@bt.com>
Date: Fri, 9 Sep 2005 20:28:30 +0100
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF2709E58D@i2km02-ukbr.domain1.systemhost.net>
To: <public-ws-addressing@w3.org>

To assist in accessing the coverage of out test suite, i've created an 
enumerated list of concrete 'message exchanges' I'd imagine seeing in
test cases:

It's likely that i've made some mistakes, in particular the use of HTTP 202 in 
the absence of a SOAP 1.2 one-way binding, and when sending 
a Fault as a callback, so some working group review would be much

This owes much to Microsoft's test scenarios for the member submission:

as well as Dave's list of scenarios from the async TF:

As you can see, this concentrates on SOAP message exchanges over HTTP. 
The async TF identified another class of scenarios over a 'one-way 
transport', i.e. a message path with no natural back-channel. For SOAP 
1.2 we have Email binding, but given the difficulties in finding 4 
implementations which interoperate over SMTP, JMS, MQ Series, UDP, 
Jabber etc, we may decide that such a demonstration isn't required for CR, 

However there is nothing to prevent us from recording such test cases in
our suite and it would be nice to at least have some test cases for 
the SOAP 1.2 Email binding:

Also it would be nice if for the test you submit, you cite the id of 
the message exchanges which it could be applied to, e.g. Hugo's recently 
submitted test case:

specifically exhibits the 'SOAP12-HTTP-In-Out-Fault' message exchange:

I've updated the test suite submission advice to reflect this, and 
have been working on other meta-data useful when contributing
test cases:


Received on Friday, 9 September 2005 19:28:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:11 UTC