RE: Q: Dependent Initialization

"Berin Loritsch" <[email protected]>
Newsgroups gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel
Message-ID <[email protected]>
> From: [email protected] [mailto:[email protected]]On Behalf Of Greg
> 
> >>>>> "Berin" == Berin Loritsch <[email protected]> writes:
> 
>     Berin> In Fortress, if any component needs another one during init
>     Berin> time, then the dependent component is initialized 
> on demand.
>     Berin> Otherwise, components are initialized according to 
> the order
>     Berin> in the backing map.  The approach worked well for the ECM,
>     Berin> and it was brought forward to Fortress.
> 
> Berin, I always ment to aks that: what does Fortress do to prevent
> initialization loops? ECM simply went into an infinite loop AFAIR.


Good question.  I have never written anything with a circular dependency.
In general that's a *really* bad practice.  Unfortunately you can't keep
people from shooting themselves in the foot.

I'm not sure if I have infinite loop protection in there or not.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.