Re: WSO2 results and GZip trouble.

Hi Jonathan,

Just had a look at WSO2 results. Seems like there were a few problems in the
test framework. The following are those messages

10) in MessageTestFault, wsoap:code="#any". If wsoap:code is not set we
axis2 uses soap:Sender by deafult. This makes the http status code 400 in
the responce. But the test framework assumes its 500.

18) same problem as 10

22) same problem as 10

24) same problem as 10

32) same problem as 10

36) same problem as 10

38) same problem as 10


So if this is fixed we should see a lot more green

Thanks,
Keith.
On 1/12/07, Jonathan Marsh <jonathan@wso2.com> wrote:
>
>  I just checked in updated WSO2 results [1] (at last – had to reinstall
> Windows today…)
>
>
>
> The gzipped test screws things up a bit more than I thought it would –
> apparently the logger just dumps it into <messageContent> as a binary
> stream, resulting in non-well-formed XML.
>
>
>
> I had to manually remove the binary in order for the .wsimsg to parse.  I
> checked in the raw under .wsimsg.raw for experimental purposes
> (results-messages/MessageTest-1G).
>
>
>
> Perhaps there's some ANT magic that can strip out the binary, stick it in
> a file, unzip it, and put it back in (along with an annotation indicating
> the unzip occurred.)
>
>
>
> [1]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/results-messages/Message-tests-results.html<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/test-suite/results-messages/Message-tests-results.html>
>
>
>
> *Jonathan Marsh* - http://www.wso2.com -
> http://auburnmarshes.spaces.live.com
>
>
>
>
>