> Yes, I'm going to propose jakarta-turbine-plexus as the place for us to > work on the container. That will be for the core, I'm not sure where we > will put the components as plexus will work completely with dynamically > loadable/reloadable components. It works right now, but I'm working with > Peter Royal to make the whole thing dynamic from ground up.
When you get to the documentation, could you include a small bit on why Turbine needs its own container? I trust that a new container is needed since you're implementing it, and I take it that it has to do with dynamic loadability, but I'm just curious. I'm semi-following the avalon-dev list and it's probably confusing me more than anything, but I get there are several containers (EMC, Phoenix, Fortress, and Merlin...now Tweety and MicroContainer?). It might be something the Avalon guys should write up, but a comparison of the different containers would be really awesome...features/pros/cons/future plans, etc. Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
