Ole,
Phoenix usually creates a fixed number of blocks at startup
and distributes
them to each other according to the assembly.xml.
But this is just too static for me. I need a way to
dynamically create new
blocks at runtime.
Do you really need blocks? Or are you talking about block managed
components ?
Call it blocks, components, services, XXX, ...
Unfortunately there is large distinction...
I won't mind. I just would like to be able to get a new Instance of a XXX
without having to deal with its implementation or the life cycle.
Of course it would be nice if the thing doing this would be able to honor
the same configuration files as the container. Otherwise the break could be
too big.
Sounds like (inside block) :
Object o = new OtherBlock();
o.someMethod();
That is not IoC I'm afraid.
EOB (eob.sourceforge.net) manages ints own components (beans)
internally. In honors a number of the Avalon-Framework interfaces.
I took a look at it but it seems not to support the same meta information
files as Phoenix (assembly.xml, *.xinfo) and it seems to be a totally new
container (no code reusage, ...).
Yes it is a container within a container. Yes it is new. It is not
meant to replace phoenix or honor its its blocks. It introduces a new
componet model (beans, inspired by EJB).
But the thing that makes it a "no, no" to me is that it isn't in production
stage.
I was not suggesting you use it :-)
I switched to Phoenix because it is the only container that has a product
status and is quite modern so I don't have to fear every Avalon update.
I agree that was correct for you to do.
I think I will take a look at making a simple generic factory or even very
simple non-generic factories.
Unfortunately I am still in the dark. Smarter people than me, and there
are plenty in here, must help you...
P.S.: The concept of EOB looks nice. :-)
Thanks.
- Paul
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
