Hi Stephen,
Thanks for info, but you don't answer those question :
* How/When custom container could know/manage context of sub-component?
* How/When custom container could acquire reference to ready to use
sub-component ?
> One problem in the above - Merlin 2.1 does not directly support the
> Executable interface. Problem is that the semantics at the level of
> the framework are fuzzy here - what to do if a component implements
> Executable and Startable? My own thoughts are that this should
> qualified as a deployment policy - such that policy (a) results in
> invocation of Startable and policy (b) ignores startable and only
> invokes Executable. Policies (a) and (b) should be mutually exclusive.
One case when I have Startable and Executable :
then component is scheduled (schedule actived with start) but I need the
ability to run the action handly, so I use execute() (through JMX or other
component).
I'm OK with you, Executable is out of the scope of the Container but aren't
exclusive with Startable.
> I'll put together a tutorial that demonstrates a custom container.
Thanks.
I wrote a HelloContainer but I don't see the difference between Container
and component (if container couldn't use, compose sub-component).
--------------------------------------------------------------
David "Dwayne" Bernard Freelance Developer (Java)
mailto:[EMAIL PROTECTED]
\|/ http://dwayne.java-fan.com/
--o0O @.@ O0o-------------------------------------------------
----------------------------------------------------------------
Ce service de mailing vous est offert par http://www.freesurf.fr.
FreeSurf, votre acces ADSL a partir de 29 euros/mois
http://www.freesurf.fr/adsl/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
