> A component developed against a set of (one or more) specifications
> WILL work unmodified in all applications that understand/"complies
> with" suc specification(s).
That is like saying that a J2EE component will run on every J2EE app server.
Very nice, but doesn't do much for J2SE or J2ME. Essentially, you are
saying that only an Avalon "J2EE" can/should exist.
> Once components can be "managed" inside and outside applications, it
> will drive applications in many directions, where containers are only
> one such branch of development. The better the tools, the faster
> components can be created, leading to more tool support and so on.
Perhaps, but entire application domains are removed from being able to use
Avalon, which eliminates their communities, and anyone who is aware of the
politics within this project would be increasing loathe to build using its
technology. Existing projects are starting to look at exit strategies.
I think that Alex had the right idea at a time before the Directory code was
encumbered. James is too dependent on Avalon for safety. We are going to
have to decouple it, using an approach similar to what Alex has done, in
order to ensure that James has options.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
