If we decide on this, we can go on and re-factor the services to fit the rich (and optional) life cycles that Avalon Framework provides.
Then we can find one of the Avalon containers to use, or write our own. I think that the Avalon folks would aim us at Merlin or Fortress, not Phoenix.
In my current project, we are currently taking this approach, and are probably going to write our own container for Avalon Framework services. The services don't care what the container is as long as it plays the full and correct Avalon Framework game. My project's needs are probably strange enough to justify our own container. It's not so hard to create a good, simple Avalon container.
Now, this is just for services, not for a micro-kernel, which is more like what Phoenix gives, I think. I'm not sure Jetspeed needs a micro-kernel, since it's basically a servlet with many services and Pluto. What I think we need is a service model to replace Turbine, and I like Avalon Framework.
And we might be able to either retro-fit Pluto to use Avalon services, and then either use Pluto's service container or our own as an Avalon container. Just thinking here...
- Glenn
On Wednesday, October 15, 2003, at 10:50 AM, Weaver, Scott wrote:
I have been evaluating component/service/kernel frameworks. So far, I really like what I see in Avalon Phoenix, it seems right down the alley of what we are trying to accomplish. It also has built-in in JMX to manage components.
I briefly looked at picocontainer, very cool, however it is somewhat
young where as Phoenix has quite a few projects built upon it, including
Apache James. Same goes for Hivemind with respect to being a less
mature project.
I would love if everyone who has used/researched any of these products give me a summary of their findings/experiences so as we can make the best choice for Jetspeed.
I realize we had a recently discussed this in passed thread, but I want to keep this alive as we need to make this decision very soon. Plus, I want to have as much community involvement/input on this choice as possible.
Regards, ________________________________ | | | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | |________________________________|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
