||An Authenticator is a component (usually a Valve or Container) that
provides some sort of authentication service.
||A Cluster works as a Cluster client/server for the local host
Different Cluster implementations can be used to support different
ways to communicate within the Cluster.
||Decoupling interface which specifies that an implementing class is
associated with at most one Container instance.
||A Container is an object that can execute requests received from
a client, and return responses based on those requests.
||Interface defining a listener for significant Container generated events.
||A ContainerServlet is a servlet that has access to Catalina
internal functionality, and is loaded from the Catalina class loader
instead of the web application class loader.
||A Context is a Container that represents a servlet context, and
therefore an individual web application, in the Catalina servlet engine.
||An Engine is a Container that represents the entire Catalina servlet
||Abstract representation of a group of
Users in a
||A Host is a Container that represents a virtual host in the
Catalina servlet engine.
||Interface defining a listener for significant events related to a
specific servlet instance, rather than to the Wrapper component that
is managing that instance.
||Common interface for component life cycle methods.
||Interface defining a listener for significant events (including "component
start" and "component stop" generated by a component that implements the
||A Loader represents a Java ClassLoader implementation that can
be used by a Container to load class files (within a repository associated
with the Loader) that are designed to be reloaded upon request, as well as
a mechanism to detect whether changes have occurred in the underlying
||A Manager manages the pool of Sessions that are associated with a
||Interface describing a collection of Valves that should be executed
in sequence when the
invoke() method is invoked.
||A Realm is a read-only facade for an underlying security realm
used to authenticate individual users, and identify the security roles
associated with those users.
||Abstract representation of a security role, suitable for use in
environments like JAAS that want to deal with
Server element represents the entire Catalina
||A Service is a group of one or more
Connectors that share a single Container
to process their incoming requests.
||A Session is the Catalina-internal facade for an
HttpSession that is used to maintain state information
between requests for a particular user of a web application.
||Interface defining a listener for significant Session generated events.
||A Store is the abstraction of a Catalina component that provides
persistent storage and loading of Sessions and their associated user data.
||Abstract representation of a user in a
||Abstract representation of a database of
Groups that can be maintained by an application,
along with definitions of corresponding
referenced by a
Realm for authentication and access control.
||A Valve is a request processing component associated with a
||A Wrapper is a Container that represents an individual servlet
definition from the deployment descriptor of the web application.
||General event for notifying listeners of significant changes on a Container.
||Global constants that are applicable to multiple packages within Catalina.
||General event for notifying listeners of significant events related to
a specific instance of a Servlet, or a specific instance of a Filter,
as opposed to the Wrapper component that manages it.
||General event for notifying listeners of significant changes on a component
that implements the Lifecycle interface.
||ServerFactory allows the registration of the
Server instance for this JVM, so that it
can be accessed independently of any existing reference to the
||General event for notifying listeners of significant changes on a Session.