RE: FYI: Updated all test-suite results

Yes, any use of <infault> in the message tests is incorrect, I've removed it
everywhere in the test cases, eliminating the EchoStringInFault operation,
the associated fault and schema type, and orphaned <infault>s in other
operations.  Should be a simpler and cleaner test now.

'sides, couldn't break my record of screwing up the interchange results just
as they go penultimately green ;-).

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: Youenn Fablet [mailto:[email protected]]
> Sent: Monday, January 22, 2007 8:11 PM
> To: Jonathan Marsh
> Cc: 'www-ws-desc'
> Subject: Re: FYI: Updated all test-suite results
> 
> Please find updated interchange and exchange results.
> I tried to exchange messages with ww2.wso2.org:8090 but failed to
> connect to the server :(
> I still have an issue with ModuleComposition-1G use case:  the
> EchoStringInfault operation is assumed to send an infault.
> I thought we decided to remove this case. To correctly test the
> operation after this one, I used EchoStringOutFault in lieu of
> EchoStringInFault in the logs.
> Regards,
>     Youenn
> 
> 
> Jonathan Marsh wrote:
> >
> > Including test-coverage, validation, the whole shebang.
> >
> >
> >
> > I corrected a dozen or so TestMetadata.xml files that were claiming
> > assertions no longer in the spec (which sometimes took some
> > archaeology to determine what assertions they now violated).
> >
> >
> >
> > **Jonathan Marsh** - http://www.wso2.com -
> > http://auburnmarshes.spaces.live.com
> >
> >
> >
> >
> >