[Apache Avalon Wiki] Updated: ContainerStory

[si...@avalon.apache.org]

   Date: 2004-07-12T18:06:09
   Editor: 129.41.18.137 <>
   Wiki: Apache Avalon Wiki
   Page: ContainerStory
   URL: http://wiki.apache.org/avalon/ContainerStory

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -62,9 +62,14 @@
 
 For the sake of completeness, we should also mention '''Tweety''' which was a very basic container developed for the sole purpose as a teaching tool.  Tweety has since been abandoned, but not quite forgotten...
 
-== Picking Your Container ==
+== Container Bonanza ==
 
 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 fulfill the varied needs for containers.  The story of Avalon and related containers is certainly not yet finished.
+== The Saga Continues ==
 
+In 2003 and early 2004, there is a plenty of infighting within the Avalon community, resulting in one of the core developers being expelled, Phoenix to fork into Loom (at loom.codehaus.org) and finally a vote for "A Single Unified Platform", which passed. The vote put the lid on for a while, but not for long. More infighting arose, and various solutions were presented, which eventually resulted in the creation of Excalibur top level project (excalibur.apache.org). Excalibur TLP took over the development of Excalibur and Fortress (Phoenix had evolved too much as Loom to be bothered to 'come back'). This allowed Avalon to concentrate on its mission to provide solutions for truly inter-operable components.
+
+= One Specification, One Reference implementation =
+
+So the choice has become simple. Avalon will continue to provide solutions to make life easier for the application developer, by truly reusable and inter-changable components. The specifications still need a lot of work, but the reference implementation, Merlin, is a stable and capable container. For users the question "Which container?" no longer needs to be asked. We can all pull together and work on the Single Unified Platform, without redoing the work for several containers, each with their own variations and quirks.

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org