Whichs phases a container should exposes to enable developers to hook up and extend the lifecycle of components?
I thought about supporting - Creation (after instantiation?) - Configuration (before configure???) - Destruction (before dispose) Thoughts? To manage extensions I created a LifestyleManager class that exposes events. I would like to enable Context/Contextualization in Avalon.Net through extensions as an eat-your-own-dog-food exercise. Anyway every ComponentFactory should rely on LifestyleManager class as a handler. I don't know how to do that in a non- intrusive way and not dependent of a correct ComponentFactory implementantion to everything works fine. Help!!! hammett --- Acabe com aquelas janelinhas que pulam na sua tela. AntiPop-up UOL - � gr�tis! http://antipopup.uol.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
