Hi, we are having a slight problem with the initialization of components. The scenario is like this:
We have a number of components that we define in the block.xml and that all have the same component class, but they are not necessarily present in all configurations (it's hardware wrappers in different machine setups). Via a lifecycle extension all classes are registered in a manager. Now, another component gets a reference to the manager via the ServiceManager, but the list of lifecycle-stage-gathered components is still empty at that time, since custom stages are executed oafter the build-in ones. The question is, how do we solve that? I see several possibilities: 1. Skip the manager and declare every interested part as a provider of the appropriate lifecycle extension - is that possible or will just one provider be choosen, forcing you to provide a number of "slot"-stages for components to aquire? 2. Make direct dependencies via the Service manager and try to do the choosing via the setup/block.xml - the dependencies are no longer loosely coupled since there must be at least one implementing component in the system at all times. 3. Provide a observer interface in the manager in order to be able to do a callback to interested components when the interesting components enter via the lifecycle extension - feels like we would be replicating the exact mechanism of merlin once more :/ What do you think is a good plan? Cheers /peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
