Overview

Excalibur is organised very modularly, as you would expect from a component-oriented project. Containerkit contains several standalone libraries which are used to build our containers, and potentially those of external projects.

If you are not building or customizing your own container, your use for these libraries will probably be somewhat limited.

Stable libraries

PackageDescription
Instrumentation

Excalibur Instrument is an instrumentation utility that allows you to attach a separate JVM to your running application to determine its health. Instrumentation is the process of exposing the internal state in a way that is easy for an administrator or help desk personell to digest. Excalibur Instrumentation is such a package that you can use for your Avalon based projects.

Excalibur-Fortress supports instrumentation.

Lifecycle

The Lifecycle package contains a set of interfaces and classes supporting portable lifecycle extensions.

Contributions to this project are based on co-development actives by container projects aiming towards cross-container component portability and consistent service management.

Excalibur-Fortress supports lifecycle extensions.

Logger

Find Avalon Excalibur's Log Management System in the org.apache.avalon.excalibur.logger package. Excalibur-Logger integrates neatly into the Avalon ECM and Excalibur-Fortress. The main goal is to be able to define the log categories on a component basis by specifying a 'logger' attribute which denotes the log category to use for a particular component (given the component is LogEnabled or Loggable).

Generic components

Please see this page for information on more generically reusable components (for example, Excalibur-Monitor and Excalibur-Datasource).

Deprecated libraries

Please see this page for information on older libraries that have been deprecated.