> From: Marcus Crafter [mailto:[EMAIL PROTECTED]] > > When I get a component from a CM or the handler inside > the CM, I don't > know if that component was created just then, or if it > was simply > pooled and retrieved. > > This makes a difference if you want to add a new lifecycle stage > to the instantiation phase of a component where it > should be done > only once during startup, perhaps after the standard > avalon stages > - or if you want one done at the access level, in which case it > needs to be done on every lookup.
It shouldn't make a difference. The three phases that are currently supported and documented are: Initialization (bring the component to life) Active Service (use the component) Destruction (kill the component) There is nothing else. And in the future Avalon 5, there will be no notion of release() in a component's lifecycle. I think that any such mechanism should work with this constraint. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
