Products

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 Phoenix focussed on very different approaches to component management. The ECM model dealt with primarily pooled objects used in environments such as Cocoon . The Phoenix 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.