Leo,
> > Point of the picture is that I hope the big box ("Avalon Container /
> > Kernel") could be flexible enough to meet your design ideas.
> > In fact, there could easily be multiple implementations of
> > this beast. One might look very similar to what Merlin is
> > now (started up by the Repository) while another might look
> > like your "myContainer" example. The parts inside would be
> > (somehow) completely pluggable and several should be optional.
> >
> > Thoughts?
>
> Looks like what I want, except the "Facilities" are also "aspects".
>
> For example, the respository:
>
> An aspect that either:
>
> + listens to events applianceAdded/applianceRemoved
>
> + when triggered by some external input
>
> Tries to validate the dependencies in the container (see my email
> to Alex about that), and for the unresolved deps, starts adding
> appliances (component handlers) by going to the local or remote
> respository.
>
> The HTTP interface:
>
> Scans for HTTPAware component handlers and exposes them.
>
> Managing POJOs:
>
> POJOComponentHandler / POJOAppliance
>
> And so on...
>
> It seems like we're on the same track.
>
> /LS
Excuse the one liner but this is marvelous news.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
