Cornerstone Collection

Delivered-To: mailing list cvs@avalon.apache.org Received: (qmail 60570 invoked by uid 500); 27 Oct 2003 13:23:03 -0000 Received: (qmail 60567 invoked from network); 27 Oct 2003 13:23:03 -0000 Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by daedalus.apache.org with SMTP; 27 Oct 2003 13:23:03 -0000 Received: (qmail 73008 invoked by uid 1438); 27 Oct 2003 13:23:05 -0000 Date: 27 Oct 2003 13:23:05 -0000 Message-ID: <20031027132305.73007.qmail@minotaur.apache.org> From: mcconnell@apache.org To: avalon-sandbox-cvs@apache.org Subject: cvs commit: avalon-sandbox/mavenized-site/xdocs/product/framework index.xml navigation.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N mcconnell 2003/10/27 05:23:05 Added: mavenized-site/xdocs/product/components index.xml navigation.xml mavenized-site/xdocs/product/containers index.xml navigation.xml mavenized-site/xdocs/product/framework index.xml navigation.xml Log: Add product docs. Revision Changes Path 1.1 avalon-sandbox/mavenized-site/xdocs/product/components/index.xml Index: index.xml =================================================================== Stephen McConnell Cornerstone Collection

Topic	Description
Cornerstone Collection	The cornerstone project is the home of a set of utility components that can be used to simplify application development. These components and typically singleton components that represent structural building blocks.
Excalibur Utilities	TO BE DONE

1.1 avalon-sandbox/mavenized-site/xdocs/product/components/navigation.xml Index: navigation.xml =================================================================== Apache Avalon 1.1 avalon-sandbox/mavenized-site/xdocs/product/containers/index.xml Index: index.xml =================================================================== Avalon Documentation Team Apache Avalon Container Solutions

Within Avalon their are a number of container solutions. This reflects a historical divergence and a present convergence within the area of containment technology within Avalon. The original containment solutions ECM and Phoneix focussed on very different approaches to component management. The ECM model dealt with primarily pooled objects used in environments such as Cocoon. The Phoneix model dealt with a strict singleton model supporting project such as James. Recent developments have resulted in the release of Fortress and Merlin. Fortress replaces the ECM solution and is positioned as a migration vehicle for components to move towards Avalon's latest container - Merlin. The Merlin container is an attempt at being a flexible and adaptive embedded container that leverages a set of common containment facilities. Merlin provides support for legacy Phoenix components and includes many of of the lifestyle concepts introduced within Fortress.

Product	Description
Avalon Merlin	The Merlin project deals with the broad area of service and component management. The Merlin system is a container that provides comprehensive support for the management of complex component-based systems. Merlin uses a component meta-model to facilitate the automated assembly and deployment of simple and composite components.
Avalon Fortress	Fortress contains a framework to help you create your own avalon containers. It boasts asynchronous management of your component instances, high scalability, easier maintenance of your code, and easy embedding into various environments like servlet engines.
ECM	This package contains the ExcaliburComponentManager (ECM). ECM has been depricated in favour of the new Fortress container.
Phoenix	Phoenix is a micro-kernel designed and implemented on top of the Avalon framework. It provides a number of facilities to manage the environment of Server Applications. Such facilities include log management, classloading, thread management and security.

1.1 avalon-sandbox/mavenized-site/xdocs/product/containers/navigation.xml Index: navigation.xml =================================================================== Apache Avalon 1.1 avalon-sandbox/mavenized-site/xdocs/product/framework/index.xml Index: index.xml =================================================================== Avalon Documentation Team Apache Avalon Component Model

The Avalon Component model is made up of a combination of classic interfaces that define the artifacts exchanged between a container and a component. The requirements presented by a component to container are expressed using meta-info descriptors that are colocated with component classes. Interfaces and default implementations are described under Avalon Framework package. The meta-info descriptors and related tools are included under the Avalon Meta package.

Product	Description
Avalon Framework	The Avalon Framework consists of interfaces that define relationships between commonly used application components, best-of-practice pattern enforcements, and several lightweight convenience implementations of the generic components.
Avalon Meta	The Avalon Meta Model defines the functional structure of component types and services. A Type definition contains information about deployment and runtime dependencies together with information about the services that a component type can provide.

1.1 avalon-sandbox/mavenized-site/xdocs/product/framework/navigation.xml Index: navigation.xml =================================================================== Apache Avalon --------------------------------------------------------------------- To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org For additional commands, e-mail: cvs-help@avalon.apache.org