Jakarta main

Avalon main

About


Patterns and Design


The API


Avalon Developer Design Documentation

Avalon Developer Design Documentation



Introduction

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.

What that means is that we define the central interface Component. We also define the relationship (contract) a component has with peers, ancestors and children. This documentation introduces you to those patterns, interfaces and relationships.

Target Audience

This documentation is aimed towards developers who are interested in the design principles of Avalon, or wish to develop code that will be incorporated into Avalon.


Theoretical Aspects of Component Development

The following documents provide basic theoretical concepts that are applied through-out Avalon's framework. It would be good for a prospective developer to be at least passingly familiar with the concepts outlined in this document. The documentation also provides links to outside sources which can be consulted for further information.

  1. Patterns
  2. Reuse Standards
  3. Inversion of Control
  4. Separation of Concerns
  5. Security

Concrete Descriptions of the Avalon Component model

This section describes concrete examples of how the theoretical ideas are applied within the context of Avalon.

  1. What is a Component?
  2. What is a Composer?
  3. The Component Lifecycle
  4. Designing a Component




Copyright ©1999-2002 by the Apache Software Foundation. All Rights Reserved.