org.apache.catalina: public interface: Engine

org.apache.catalina
public interface: Engine [javadoc | source]

All Implemented Interfaces:
Container

All Known Implementing Classes:
StandardEngine

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.

author: Craig - R. McClanahan

version: $ - Revision: 467222 $ $Date: 2006-10-24 05:17:11 +0200 (mar., 24 oct. 2006) $

Method from org.apache.catalina.Engine Summary:
getDefaultHost, getJvmRoute, getService, setDefaultHost, setJvmRoute, setService

Method from org.apache.catalina.Engine Detail:
public String getDefaultHost() Return the default hostname for this Engine.
public String getJvmRoute() Retrieve the JvmRouteId for this engine.
public Service getService() Return the `Service` with which we are associated (if any).
public void setDefaultHost(String defaultHost) Set the default hostname for this Engine.
public void setJvmRoute(String jvmRouteId) Set the JvmRouteId for this engine.
public void setService(Service service) Set the `Service` with which we are associated (if any).