-----Mensagem original----- De: Leo Sutic [mailto:[EMAIL PROTECTED]
> The point of doing that is that if the Handler had been a PicoHandler > instead of an A4 handler, the handler *would* have used the > ServiceManager > to resolve dependencies. It just happened that the SM could be given to > the component directly in this case. The ComponentFactory - as Steve pointed out - is responsible for *more* than a simple creation of component instance; it executes every step of lifecycle. http://cvs.apache.org/viewcvs.cgi/avalon/merlin/activation/impl/src/java/org /apache/avalon/activation/impl/DefaultComponentFactory.java?rev=1.7&view=aut o In Castle there is a DefaultRuntime - that does exactly the same - and a CastleRuntime - that delegates the Creation/Destruction to Orchestrator that runs every Step of lifecycle allowing steps to be changed/removed. http://cvs.apache.org/viewcvs.cgi/avalon-sandbox/avalon-net/Castle/Castle/Co re/Orchestrator.cs?rev=1.7&view=auto #region Creation / Destruction /// <summary> /// /// </summary> /// <param name="model"></param> [ManagedOperation] public void InvokeCreatePhases( IComponentModel model ) { } /// <summary> /// /// </summary> /// <param name="model"></param> [ManagedOperation] public void InvokeDestructionPhases( IComponentModel model ) { } #endregion --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
