The nice thing about containers is: There are so many to choose ... ;-))
I am developing a single server application that should run (about) 24h a
day. So far (for the more prototype stage) I have used Phoenix for the whole
application and inside of it the Excalibur Component Manager (because of the
document "Developing with Apache Avalon"). But now I would like to make the
real production quality implementation but I still don't know which
component/service container to use. The application should be shipped during
January next year. So the container should have release quality then.
The choice seems to be:
1. Phoenix: The new official release has just come out and it
seems to support the new service stuff and the
new unified? configuration but seems to be
oversized for a single application because it is
build to host many applications.
Or is this a feature that doesn't cost any
performance during runtime (due to overhead)?
2. Tweety: Only for educational purposes and pre-alpha.
3. Myrmidon: Pre-alpha and specially made for Ant2.
4. Fortress: Pre-alpha and needs a container itself.
5. Merlin: Pre-alpha and needs a container itself.
Where is the difference to Fortress when the
unification of interfaces and configuration has
been successful????
6. Plexus: Pre-alpha, specially made for Turbine and needs a
container itself.
7. ECM: The Excalibur Component Manager seems to be
outdated now and needs a container itself.
So is it true that writing new containers has become such a popular sport
that there is none left that can be used without feeling guilty in one way
or the other??? ;-)))
So in January 2003 I would like to ship a *stable and modern* single server
application but which container should I choose???
Any help/opinion is welcome,
Ole
--
Ole Bulbuk Tel.: 0331/74759/60
Ernst Basler + Partner Fax: 0331/74759/90
Tuchmacherstr. 47 E-Mail: mailto:[EMAIL PROTECTED]
14482 Potsdam WWW: http://www.ebp.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
