Welcome to Avalon-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. In the future it will conditionally support extra facilities such as central server management, server pools, and other facilities aimed at reducing the time to market. The API defines a standard method of piecing together server components and creating a server.

Phoenix is no longer under active development. Most of the avalon container development efforts are focussed on Merlin. If you are evaluating what container to use, we suggest you try merlin first to see if it meets your needs.

Alternatively, you might want to look at Loom, which started out as a fork of Phoenix 4.1-dev and shares many of its features. Please do note that Loom is not a part of avalon nor of the ASF.

This guide starts with an architectural overview of Phoenix. Then, we identify the different roles that typically exist in daily use of phoenix. For each of these, we provide a basic guide. We finish with a complete example.

This documentation is aimed towards people who:

• wish to create applications that run within phoenix
• wish to create components (blocks) for use within phoenix
• wish to setup and administer phoenix
• are interested in the design principles of Avalon Phoenix
• wish to develop code that will be incorporated into Avalon Phoenix
• wish to reuse Avalon Phoenix concepts in their own application

1. Architectural overview
2. Development roles
3. Administrator Guide
4. Application Deployer Guide
5. JMX Management Guide
6. Server Application Assembler Guide
7. Block Developer Guide
8. Example Configuration.

Besides the Javadocs, we have the Architectural overview to look at.