Date: 2004-01-18T11:55:04
Editor: 68.66.66.23 <>
Wiki: Apache Avalon Wiki
Page: AvalonFAQ/Container
URL: http://wiki.apache.org/avalon/AvalonFAQ/Container
no comment
Change Log:
------------------------------------------------------------------------------
@@ -36,7 +36,7 @@
* As always, it depends on what you want to do. Each container has its niche.
Phoenix and Fortress have stable releases on the Avalon download site, Merlin release
candidate (RC) binaries are also available.
* Phoenix's strong point are server-like applications. That is, if you want to
build a web server, and FTP server, a new EJB container, a chat server, and so on, you
may want to try Phoenix. It's stable and there are plenty of existing Phoenix blocks
(applications) you can use as starting points. That said, you can also use Phoenix in
standalone swing applications, but that's often easier to do with Fortress.
* Fortress is a light-weight fully-compliant Avalon 4 container. It's often
called 'embeddable' partly because it doesn't come with its own bootstrapper. That
is, you'll need to write your own 'main' class to start the container. The advantage
is that you can easily start it up in just about any environment -- servlets, swing
apps, command line apps, etc. It doesn't have all the bells and whistles of Phoenix
or Merlin, but it's solid and easy to use. Fortress also replaces the older Excalibur
Component Manager, so if you have legacy code using ECM, check out Fortress.
- * Merlin is the latest and greatest and where a lot of the current action is.
Currently (late 2003), you'll have to settle for beta releases only, but it is
certainly usable and has a number of advanced features that you might find hard to
live without. Certain Avalon developers will tell you that you shouldn't bother with
anything else, but there's plenty of documentation and several small tutorials
available for you to make your own decision.
+ * Merlin is the latest and greatest and where a lot of the current action is.
Currently (late 2003), you'll have to settle for beta releases only, but it is
certainly usable and has a number of advanced features that you might find hard to
live without. Certain Avalon developers will tell you that you shouldn't bother with
anything else, but there's plenty of documentation and several small tutorials
available for you to make your own decision.If you are coming to Avalon from Fulcrum
then please note that most of the new Fulcrum components have either been converted to
run with Merlin or are in the process of conversion(according the Stephen McConnell).
== If I wrote some kind of network daemon, using TCP/IP connections I could use lots
of stuff in excalibur. How can I establish a kind of architecture where some of the
classes can be reloaded into the system without stopping the daemon? ==
* This requires a classloader above and beyond the resources available in the JDK
or any of the Avalon containers.
@@ -74,6 +74,7 @@
* provide support for component packaging. Examples of Merlin based packaging is
included in a bunch demos that are included in the CVS (just do a checkout of Avalon,
Excalibur and Sandbox, build merlin, then $demo).
* Merlin lets you do dynamic addition to the classloader but I (Stephen McConnell)
haven't tried "reloading" a classes that has changed - my gues is that some work would
be needed on the type, profile, and appliance libraries (but probably not too much).
* http://avalon.apache.org/merlin/
+ * If you are coming to Avalon from Fulcrum then please note that most of the new
Fulcrum components have either been converted to run with Merlin or are in the
process of converstion (according the Stephen McConnell).
* http://nagoya.apache.org/wiki/apachewiki.cgi?Merlin
* status (2003/03/28) : unstable
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
