W3C home > Mailing lists > Public > public-ws-addressing-tests@w3.org > March 2006


From: Glen Daniels <gdaniels@sonicsoftware.com>
Date: Wed, 15 Mar 2006 16:16:38 -0500
Message-ID: <80A43FC052CE3949A327527DCD5D6B2701986C44@MAIL01.bedford.progress.com>
To: <paul.downey@bt.com>, <dims@wso2.com>
Cc: <mark.little@jboss.com>, <public-ws-addressing-tests@w3.org>

Hi Paul:

> I'm nervous messing with the report given our PR call is 
> tomorrow however fetchlogs.pl picked up:

We're not talking about "messing with the report", we're talking about
the fact that the report as it stands is incorrect, or at the least
incomplete.  This is one of the issues with getting the results via a
small set of XPath assertions... I could post logs which violate the
SOAP schema and the report would validate them as green.

* The WSO2 logs show the aforementioned problem with WSA

* The MS->everyone logs show a) invalid SOAP (test 1170, bad MU value)
and b) invalid WSA schema (non-URI action values in 1143/1243).  Just
because most people accept these messages doesn't mean they aren't

I don't think that brushing this stuff under the carpet is going to help
anyone, either in the short run or the long run.  On the bright side,
there are going to be NO spec changes to get these issues fixed, however
the test suite and the implementations DO need to change, IMHO.

What do others think here?


> - one all green WSO2-Axis log
> - a Microsoft-Microsoft-Axis with less red, but also little
>   less green, which I elected to check in given it might
>   help Glen
> - and a 'bad' WSO2-WSO2-JBoss log file which I elected to ignore
> http://www.w3.org/2002/ws/addr/testsuite/report/ 
> Paul
Received on Wednesday, 15 March 2006 21:19:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:29:02 UTC