Berin Loritsch wrote:

I still disagree rather strongly with you.  Take a look at J2EE.  Sun
wrote the specs and the compliance testing framework.  They even have
a reference implementation--which I may add they do not recommend for
prime-time.  The real J2EE systems are written by third parties like
JBoss, BEA, IBM, etc.

I don't see how having one super-container is going to help.  I doubt
we would be able to come to one vision.  The fact that consumers have
to choose between systems with largely overlapping functionality in
J2EE systems proves that consumers are intelligent enough to find out
what their needs are.  What we need to do is provide enough information
to help the consumer make their decision.
Sun designs a framework, so does Avalon.

Sun ships *ONE* reference implementation of that framework and allows external entities to build other implementations.

Why should Avalon ship more than one reference implementation?

Cocoon is also a framework.

Tell me: if Cocoon was shipping four different implementations of the Cocoon internal interfaces for every time a new vocal developer comes in and doesn't like what the community decides, would that make it perceived as a better project from the user community?

Think about it.

--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to