avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@citi-us.com>
Subject RE: Q: Dependent Initialization
Date Fri, 20 Dec 2002 20:15:07 GMT
> From: greg@home.nest.cx [mailto:greg@home.nest.cx]On Behalf Of Greg
> 
>     Vladimir> May be this is reason to add to framework new interface
>     Vladimir> between initialization and start phases with one method
>     Vladimir> setup()? This allows to have a phase where services can
>     Vladimir> interact with live instances of other services.
> 
> If I understand you correctly, all you need to do in e.g. Phoenix is
> specify that B should be provided to A. Then B will be fully 
> initialized
> and started by the time A gets to use it. Does that answer your
> question?


In Fortress, if any component needs another one during init time, then
the dependent component is initialized on demand.  Otherwise, components
are initialized according to the order in the backing map.  The approach
worked well for the ECM, and it was brought forward to Fortress.

--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message