Date: 2004-01-10T03:37:48
   Editor: 203.10.76.38 <>
   Wiki: Apache Avalon Wiki
   Page: ContainerStory
   URL: http://wiki.apache.org/avalon/ContainerStory

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -64,7 +64,7 @@
 
 == Picking Your Container ==
 
-Now Avalon was left with a horde of containers:  Phoenix, Merlin, Fortress and the 
depricated ECM.  After a long debate on the merits of one or many containers, the 
decision was made to push for Avalon unification.  The grand container to rule them 
all would one day become a reality.  To reach this goal, Merlin has been selected as 
the "flagship" Avalon container and that is where you will find most of the action 
today.  Merlin supports a host of features and configurations, but there's still work 
to be done to fully support features still only found in Fortress or Phoenix.
+Now Avalon was left with a horde of containers:  Phoenix, Merlin, Fortress and the 
deprecated ECM.  After a long debate on the merits of one or many containers, the 
decision was made to push for Avalon unification.  The grand container to rule them 
all would one day become a reality.  To reach this goal, Merlin has been selected as 
the "flagship" Avalon container and that is where you will find most of the action 
today.  Merlin supports a host of features and configurations, but there's still work 
to be done to fully support features still only found in Fortress or Phoenix.
 
 Phoenix and Fortress will still be supported for some time to come and there will 
still be future releases and development.  In addition, there are a number of 
alternative framework similar to Avalon (such as Loom, PicoContainer, and the Spring 
Framework) which have emerged to fullfil the varied needs for containers.  The story 
of Avalon and related containers is certainly not yet finished.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to