Re[2]: [Conceptual] [Fortress] component startup order

[Anton Tagunov <at...@mail.cnt.ru>]

Hello Leo!

AT> From: Anton Tagunov [mailto:atagunov@mail.cnt.ru]
AT>
AT> In fact if we have dependency
AT>
AT>     A - > B
AT>
AT> but A has inline activation and B - background, A will
AT> still be (probably?) initialized before B.

LS> Doesn't that mean that B will be initialized as a part of A's
LS> init, as lazy init kicks in?

1)

Don't think so.
If I understand the code correctly then if A has activation policy
'inline' and B - 'background' then when A is initialized the
handler for B won't be prepared yet, will it?

2)

errr.. I seem to find I probably do not understand the code
sufficiently.. ThreadSafeComponentHandler does need
preparation, does not it? But then how does the lazy
initialization work at all?

-Anton


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