Interface Engine

All Superinterfaces:
Container, Lifecycle
All Known Implementing Classes:

public interface Engine extends Container
An Engine is a Container that represents the entire Catalina servlet engine. It is useful in the following types of scenarios:
  • You wish to use Interceptors that see every single request processed by the entire engine.
  • You wish to run Catalina in with a standalone HTTP connector, but still want support for multiple virtual hosts.
In general, you would not use an Engine when deploying Catalina connected to a web server (such as Apache), because the Connector will have utilized the web server's facilities to determine which Context (or perhaps even which Wrapper) should be utilized to process this request.

The child containers attached to an Engine are generally implementations of Host (representing a virtual host) or Context (representing individual an individual servlet context), depending upon the Engine implementation.

If used, an Engine is always the top level Container in a Catalina hierarchy. Therefore, the implementation's setParent() method should throw IllegalArgumentException.

Craig R. McClanahan
  • Method Details

    • getDefaultHost

      String getDefaultHost()
      the default host name for this Engine.
    • setDefaultHost

      void setDefaultHost(String defaultHost)
      Set the default hostname for this Engine.
      defaultHost - The new default host
    • getJvmRoute

      String getJvmRoute()
      the JvmRouteId for this engine.
    • setJvmRoute

      void setJvmRoute(String jvmRouteId)
      Set the JvmRouteId for this engine.
      jvmRouteId - the (new) JVM Route ID. Each Engine within a cluster must have a unique JVM Route ID.
    • getService

      Service getService()
      the Service with which we are associated (if any).
    • setService

      void setService(Service service)
      Set the Service with which we are associated (if any).
      service - The service that owns this Engine