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.
Interface implemented by session managers that do not keep a complete copy of all sessions in memory but do know where every session is.
An Engine is a Container that represents the entire Catalina servlet engine.
This will be removed in Tomcat 9 and integrated into
A Host is a Container that represents a virtual host in the Catalina servlet engine.
This interface is implemented by components that will be registered with an MBean server when they are created and unregistered when they are destroyed.
Common interface for component life cycle methods.
Marker interface used to indicate that the instance should only be used once.
Interface defining a listener for significant events (including "component start" and "component stop" generated by a component that implements the Lifecycle interface.
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 repository.
A Manager manages the pool of Sessions that are associated with a particular Context.
Interface describing a collection of Valves that should be executed in sequence when the
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
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
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.
PersistentManager would have been a better name but that would have clashed with the implementation name.
Callback for establishing naming association when entering the application scope.
Abstract representation of a user in a
A Valve is a request processing component associated with a particular Container.
Represents a file or directory within a web application.
Represents the complete set of resources for a web application.
Represents a set of resources that are part of a web application.
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 changes on a component that implements the Lifecycle interface.
General event for notifying listeners of significant changes on a Session.
The list of valid states for components that implement
General purpose exception that is thrown to indicate a lifecycle related problem.
Copyright © 2000-2020 Apache Software Foundation. All Rights Reserved.