Robert, I see three levels of increasingly more Magic in the container:
Single-component container (MicroContainer): Use in environments where you want to use an Avalon component in a non-Avalon program. See my separate mail about this. Big thing: No external metainfo. Embeddable Container (used to write blocks): For things like Cocoon. This is where Fortress etc. fits in. You have your metadata and so on, but the container is intended to be used inside something else - Tomcat, for example. Some external metainfo required. Stand alone container (used to assemble blocks): Phoenix. Loads of metainfo. /LS > From: Robert Mouat [mailto:[EMAIL PROTECTED]] > > perhaps something like: > > ContainerKit: utilities for handling a component that is > written according to the framework (lifecycle, metadata, > maybe custom markers, etc.). Has a well defined API. > > Fortress: embeddable (extensible) container, based on > ContainerKit. Adds features that are useful for a container > but don't affect the writing of a component (e.g. pluggable > component managers, locators, interceptors). Uses > programmatic configuration and assembly. Has a well defined API. > > Phoenix: server killer app, based on fortress. Allows > components to be configured and assembled via xml files > without writing any code. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
