Sanjiva, We need SOME evidence we are on the right track? For me it's interop service/client. We can write all the code we want, but if it can't be used then it's of no use. We can put a huge disclaimer in bold, flashing letters to send the right signal that this is just a tech preview thingy.
-- dims On Mon, 21 Feb 2005 10:24:07 +0600, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > Interop tests- doing interop tests will give the wrong signal > about M1 IMO. The objective of M1 IMO is to show progress and to > give (potential Axis) developers a consistent starting point. Its > not a statement of "ready-to-use"ness by any means; there may be, > or rather will be, significant/fundamental changes after M1. > > If we start implementing interop tests then we're telling that > we are "production ready"! Also, without encoding support echo-style > interop is really really damned good, esp. on the server side! > > Sanjiva. > > ----- Original Message ----- > From: "Davanum Srinivas" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Saturday, February 19, 2005 9:55 AM > Subject: [Axis2] typos / interop tests? > > > Srinath, > > > > Can you please rename: > > - HandlerMetaData.java to HandlerMetadata.java (lowercase 'd') > > - PhaseMetaData.java to PhaseMetadata.java (lowercase 'd') > > - OmStAXBuilderTest.java to OMStAXBuilderTest.java (uppercase 'M') > > > > Do we have any interop tests? (see http://www.whitemesa.net/) > > > > Thanks, > > dims > > > > -- > > Davanum Srinivas - http://webservices.apache.org/~dims/ > > > -- Davanum Srinivas - http://webservices.apache.org/~dims/
