> I'll be going full tilt into MicroContainer now.

cool.

> This is my world as I see it:
> 
>  + MicroContainer: Use of Avalon components without the
>    Avalon architecture.
>     
>    What I see before me are three actors:
> 
>         A user: A developer that is doing, well, something. The 
>    A component: The user just downloaded this.
>     A deadline: The user hopes to use the component in order to
>                 be finished before this.

exactly. Yup. Like "here's your javabean, load the jar into your RAD,
drop it onto the palette, click 'Find Definiton', then 'Javadocs', read
it, use it". (only without the RAD tool integration)

>    (       MicroContainer is checked in under 
>        jakarta-avalon/src/proposal/microcontainer/   )

will look later.

>  + Tweety: The simplest stand-alone container. Used to teach
>    people how to write containers without using Fortress.

and how to write components.

Think "HelloWorld", "SimpleMailSender", "FileWriterDemo"

>  + Fortress: The "embedded" level container. Think "Cocoon".

Think "ServletExec", "JavaMail", "PersistenceLayer", "SOAP"

>  + Phoenix: "Server" level. Uses Fortress.

Think "Tomcat", "James", "OpenEJB", "Axis"

> Metainfo is used by Fortress and Phoenix (not MicroContainer).
> 
>  + Anything that works in Micro, works in Fortress, Tweety and Phoenix.

Tweety should be out of the loop (ie not make this guarantee)

>  + Anything that works in Fortress, works in Phoenix.

...though it would typically require additional meta info.

> So, when going to a more sophisticated container, you *never* lose 
> anything. All you get is more features from the container. But,
> some components may not work in Micro or Fortress (they require 
> Phoenix).
> 
> Is this sort-of-kind-of the world you are living in?

yup, except we have ECM and merlin as well, and it is still cool if
phoenix is embeddable as well (ie, since there is no J2EE container that
uses it as its core, make it possible to contain it within J2EE).

And it is the world I'd like to live in; we're not there just yet =)

- Leo



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

Reply via email to