RE: Saturday Morning, 4th March

Done.  Thanks for fixing the namespace issues!  This is looking pretty
good, and I hope accurate to your expectations.

> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@wso2.com]
> Sent: Saturday, March 04, 2006 7:50 AM
> To: paul.downey@bt.com
> Cc: Jonathan Marsh; public-ws-addressing-tests@w3.org
> Subject: Re: Saturday Morning, 4th March
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paul,
> 
> Please add the 2 logs (ibm-wso2.xml and msft-wso2.xml) from [1].
> 
> Thanks,
> dims
> 
> [1] http://www-lk.wso2.com/~dims/wsalogs/
> 
> paul.downey@bt.com wrote:
> > Arun, All,
> >
> > I've been periodically slurping the logs down from people's servers,
> > in as friendly US timezone as my need to sleep allowed :)
> >
> > It takes special manual effort to processs logs sent by Email, and
> > we've seen a bunch of these sent this week during the F2F.
> > It's therefore possible regression may have been introduced on both
> > the actor and observer sides of the shop :)
> >
> > - I can't access the JBoss server (I get a timeout), and looking
> > at the attachments see we have to assemble them into the single
> > log file the report expects for each interaction?
> >
> > Still no log server from WSO2, that would be very helpful.
> >
> > So really it's not been ideal for us to work on this, this week,
> > but maybe we can all pull it together during next week.
> >
> > *IMPORTANT NOTICE*
> > As the matrix is now getting large, and time is running out,
Jonathan
> > and I have decided we can no longer accommodate ad-hoc log files
sent
> > in ad-hoc ways and formats - you need to provide a log directory on
> > a web site with one log file per interaction to all the other
parties
> > in either WS-I or our own format to make it onto the report.
> > *IMPORTANT NOTICE*
> >
> >> And also the WS-I monitor changes the wsa:To header which the
Microsoft
> >> stack does not seem to like. I'll try to make these changes over
the
> >> weekend and send updated logs.
> >
> > bizare!
> >
> >> test1152 and 1252 still needs to be fixed in the CVS repository.
They
> >> are still checking for 4 messages whereas they should only be 2.
> >
> > we've been working on that - David had a fix which we've added:
> > http://lists.w3.org/Archives/Public/public-ws-addressing-
> tests/2006Mar/0029.html
> >
> >> I cant meet tuesday morning since I'll be travelling tuesday
through
> >> thursday. I can do monday or friday morning instead.
> >
> > Monday and friday evenings aren't great for me, but I've
> > been working with Jonathan so as not to become "the weakest link"
> > and so together we can cover 2/3rs of the timezones :)
> >
> >> Can you please regenerate the report by picking up the logs for
> >> Sun->Sun, Sun->IBM, Sun->Axis, Sun->JBoss from [1] ? This will give
a
> >> better idea of the current status.
> >
> > have been doing so, Arun, maybe you'd like to add WSO2 to your
matrix,
> > and refresh the Microsoft log, it's as old as the hills:
> >
> >    Sun-Microsoft.xml 	86.9 kb 	Thu, 19 Jan 2006
03:25:08 GMT
> >
> > [1] http://soapinterop.java.sun.com:8080/wsalogs/.
> >
> > Can everyone please try to add logs for all other endpoints:
> >
> > http://www.w3.org/2002/ws/addr/testsuite/endpoints/
> >
> > State of play after our hack this morning:
> >
> > http://www.w3.org/2002/ws/addr/testsuite/report/
> >
> > still getting problems with lots of white boxes in the
> > Sun columns, can't reach the JBoss log file server and I'm still
> > getting bad prefix 'echo' from some of the WSO2 log files  which
> > breaks the processor and now makes their column all 'bad'.
> >
> >
> > Paul
> >
> >
> 
> 
> - --
> Davanum Srinivas (dims@wso2.com)
> VP/Engg, WSO2 (http://wso2.com)
> Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Cygwin)
> 
> iD8DBQFECbcfgNg6eWEDv1kRApm+AKCQAiYpShc0Kb8dFH5TDy2V1Ze2IgCfThVM
> R2u+T7FveNIR6gvkYSCePU0=
> =zGnO
> -----END PGP SIGNATURE-----

Received on Sunday, 5 March 2006 00:01:53 UTC