Peter,
On Thu, 8 Mar 2001, Peter Donald wrote:
> I already work on commons packages - after all I work on Avalon ;)
Avalon is not a commons package, it is a "common framework for server
applications". Why does the framework need to contain code to accomplish
specific tasks?
What Ted proposes is the creation of a "Commons" library that will hold
utility APIs that will be useful in every Jakarta project, including
Avalon. Avalon and the "Commons" proposal are not at odds - they are
compliments.
Avalon codebase provides a framework for developing modular server
applications. Avalon should be able to peacefully coexist with a library
of utility code such as Ted proposes. For example, if a developer wanted
to create a "Connection Pool" Block they could easily develop a wrapper
Block component, and a meta-info description file.
I don't see how Ted's proposal is at odds with the Avalon project.
Wouldn't having a "Commons" library make it much easier to expand Avalon?
Tim O'Brien
[EMAIL PROTECTED]
PS: Congratulations to the new PMC
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
