Christian Heller wrote:
> On Monday 04 February 2002 15:02, you wrote:
>
>>The Reconfigurable/Recontextualizable offer container managed rewriting, or
>>updating. It is not always practical to have the container manage all
>>aspects of the configuration in the container--although it is completely
>>practical and correct to do that for composable.
>>
>>The Component cannot rewrite or change the Context or the ComponentManager
>>in any way, nor should it. It does require some limited ability to rewrite
>>the configuration information as one configuration does not fit all
>>implementations of an interface.
>>
>
> Well, perhaps there are exceptions. Ever heard/read about the "HMVC"
> pattern? http://www.javaworld.com/javaworld/jw-07-2000/jw-0721-hmvc_p.html
> Following this pattern, any of Jakarta's Components (in HVMC "Controller")
> would be a ComponentManager at the same time and any Component would have
> access to its parent (container) using "getParentController()".
I am not in favor of any child able to abtain a reference to the parent
directly. This violates IOC, and can provide some serious security problems
in systems that dynamically load and use Components. There is good reason
why all our systems force one way interaction. Whatever we do, we have to
maintain the contract that the Container manages the COmponent in a manner
that the Component cannot control how it is managed.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
