> > This seems terribly complicated as compared to the approach of a
> > component declaring what it needs
> Only if it is important to provide a per-component set of resources. That
> is the Avalon way, but it is not the J2EE way.
Actually, I'll go further than my earlier statement. A context that
contains just the things that a component declares as needing is secure, but
limited (deliberately so). With JNDI, any resource reachable from the
context can be accessed, assuming authorization. That is dynamic, without
requiring reconfiguration of the context.
There has been talk of allowing A5 contexts to be more dynamic, with a whole
subcontext model, but no resolution as far as I know, plus that is quite far
away. And I don't recall anyone indicating that A5 contexts would be
mutable by components.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
