All, thank you very much for your help. I think I know now how I will handle this (see below).
> My first thought when reading this was: > > 1. Leave those components that do no harm to be managed by > Phoenix directly. Yep. Thats what I will do anyway. > 2. Instead of writing a factory for those expensive > components, why not let > them be managed by the Excalibur Component Manager (or a > custom derivative, > if more applicable), which is - after all - a component that > could, in turn, > be managed by Phoenix? That is exactly how I have done it before. I have made a simple ExcaliburComponentManagerFactoryBlock (what a lengthwise almost german word ;-)). But I wouldn't like to use ECM anymore (since it is deprecated). And I didn't find a really nice and stable replacement. Plus all the other containers that might be stable enough don't use the same meta file formats of Phoenix (assembly.xml and *.xinfo). So administrators and my codevelopers (and of course myself) have to learn two different formats and the information is scattered over several files. I don't think that would be really good. But there seems to be another simple way: The functionality of all the components I am talking about has to run without Avalon in a simple client application too. So all the components/blocks are just wrappers around the classes with the real functionality. If I transform these wrappers to factories (which would be quite simple) all the problems should vanish. The factories are blocks and get all the lifecycle handling from Phoenix. They can pass the configuration information, context information, etc. as parameters to the constructor of the real class (they are doing this already but just once). This way I use Phoenix in the way it should be, have got all the meta information in a consistent format and finally use only one container/component manager that has got a production status and is (hopefully ;-) not deprecated any time soon. Regards, Ole -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
