Re: thoughts on Avalon PMC

[Paul Hammant]

Berin

Let's take the cue from J2EE.  Sun developed the SPECIFICATIONS.  The
rules, regulations, and contracts of a compliant container.  That should
be the goal and focus of the Avalon component framework.

Not to have a supercontainer to end all containers.  Such a beast would
not work well in embedded environments anyways.  There is a reason for
separate containers.  The thing is that we need to make it so that any
component will work reasonably in any of the Containers.

Amen.

In my option that specification is Avalon-Framework's lifecycle interfaces.

Whether a conatiner uses XML to lace comps together or has _no_ such meta lacing, or what particular design for the XML is completely irrelvent to that quest.

-ph


--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>