xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Theodore W. Leung" <twle...@sauria.com>
Subject Re: [POLL] WASP Lite on Apache?
Date Thu, 15 Nov 2001 06:33:36 GMT
On Wed, 2001-11-14 at 14:14, Sam Ruby wrote:
> Theodore W. Leung wrote:
> >
> > I am *very* against the idea of WASP as a separate project.  If the Axis
> > and Wasp communities can not agree, then I think we're done.
> What if the Axis and Wasp communities agree that separate code bases are
> the right initial step?

I was stating my opinion -- if the Axis and Wasp communities decide that
separate code bases is the right thing, then of course I respect that --
I would suggest in that case that there be some visible plan for how
those code bases integrate.

> > I think that the WASP code and community can contribute in a number of
> > areas.  The way that we got into the Crimson / Xerces mess was that we
> > said, we'll accept both projects and figure out how to merge them
> > later.  It took a long time for that to start to happen -- not that it's
> > fully happened just yet.
> Let's not extrapolate too much from one data point.  I would suggest that
> there were other factors involved too.

Yes there were.  And some of them apply here too.  Namely Sysinet and
IBM both having investment in existing code bases.

> > The way that Batik happend
> If I understand correctly, Batik was "x" number of companies getting their
> code integrated outside of the scope of Apache, and then contributing the
> result?  


> Given that Axis is already an Apache code base, how should we
> proceed?

I'd be very happy to see a JAX RPC and JAXM compliant SOAP stack on
Apache.  If the Wasp stack turned out to be closer, would the Axis
community be willing to orphan the Axis code base and do the work to
bring the Wasp stack up to spec?  If the Axis stack turns out to be
closer, are the Wasp folks willing to drop the Wasp stack and adapt the
rest of Wasp to Axis?

I can live with two code bases for a defined period of time.  What I
would not like to live with is an uncertain direction and/or unbounded
timeframe for those two code bases.  I think that in the end there needs
to be a single SOAP code base, and that part of the process for the
contribution should be a reasonable plan for how to get there.   


In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org

View raw message