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 |
|---|---|
|
The Avalon Framework API and Implementation 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. |
|
|
The Avalon Meta Model defines the functional criteria for 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. |
|
|
A set of utilities shared by framework components supporting default property management, environment variable resolution, exceptio reporting and a parameterized map implementation (using within the repositroy package). |
|
|
A joint initative by the Avalon Project and the Apache Directory Project in the development of an inteligent bootstrappig, resource replication, and artifact management framework. |
|
| Avalon Logkit |
Logkit is a complete logging framework (like log4j) as an Avalon component. Most Avalon containers use it as the default logging implementation. |
