Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> apache >> catalina >> [ core Javadoc ]

• org.apache.catalina.core: Javadoc index of package org.apache.catalina.core.


Package Samples:

• org.apache.catalina.core

Classes:

• ContainerBase: Abstract implementation of the Container interface, providing common functionality required by nearly every implementation. Classes extending this base class must implement getInfo() , and may implement a replacement for invoke() . All subclasses of this abstract base class will include support for a Pipeline object that defines the processing to be performed for each request received by the invoke() method of this class, utilizing the "Chain of Responsibility" design pattern. A subclass should encapsulate its own processing functionality as a Valve , and configure this Valve into the pipeline ...
• ApplicationHttpResponse: Wrapper around a javax.servlet.http.HttpServletResponse that transforms an application response object (which might be the original one passed to a servlet, or might be based on the 2.3 javax.servlet.http.HttpServletResponseWrapper class) back into an internal org.apache.catalina.HttpResponse . WARNING : Due to Java's lack of support for multiple inheritance, all of the logic in ApplicationResponse is duplicated in ApplicationHttpResponse . Make sure that you keep these two classes in synchronization when making changes!
• ApplicationHttpRequest: Wrapper around a javax.servlet.http.HttpServletRequest that transforms an application request object (which might be the original one passed to a servlet, or might be based on the 2.3 javax.servlet.http.HttpServletRequestWrapper class) back into an internal org.apache.catalina.HttpRequest . WARNING : Due to Java's lack of support for multiple inheritance, all of the logic in ApplicationRequest is duplicated in ApplicationHttpRequest . Make sure that you keep these two classes in synchronization when making changes!
• ApplicationResponse: Wrapper around a javax.servlet.ServletResponse that transforms an application response object (which might be the original one passed to a servlet, or might be based on the 2.3 javax.servlet.ServletResponseWrapper class) back into an internal org.apache.catalina.Response . WARNING : Due to Java's lack of support for multiple inheritance, all of the logic in ApplicationResponse is duplicated in ApplicationHttpResponse . Make sure that you keep these two classes in synchronization when making changes!
• ApplicationRequest: Wrapper around a javax.servlet.ServletRequest that transforms an application request object (which might be the original one passed to a servlet, or might be based on the 2.3 javax.servlet.ServletRequestWrapper class) back into an internal org.apache.catalina.Request . WARNING : Due to Java's lack of support for multiple inheritance, all of the logic in ApplicationRequest is duplicated in ApplicationHttpRequest . Make sure that you keep these two classes in synchronization when making changes!
• ApplicationDispatcher: Standard implementation of RequestDispatcher that allows a request to be forwarded to a different resource to create the ultimate response, or to include the output of another resource in the response from this resource. This implementation allows application level servlets to wrap the request and/or response objects that are passed on to the called resource, as long as the wrapping classes extend javax.servlet.ServletRequestWrapper and javax.servlet.ServletResponseWrapper .
• StandardPipeline: Standard implementation of a processing Pipeline that will invoke a series of Valves that have been configured to be called in order. This implementation can be used for any type of Container. IMPLEMENTATION WARNING - This implementation assumes that no calls to addValve() or removeValve are allowed while a request is currently being processed. Otherwise, the mechanism by which per-thread state is maintained will need to be modified.
• ApplicationFilterChain: Implementation of javax.servlet.FilterChain used to manage the execution of a set of filters for a particular request. When the set of defined filters has all been executed, the next call to doFilter() will execute the servlet's service() method itself.
• StandardEngine: Standard implementation of the Engine interface. Each child container must be a Host implementation to process the specific fully qualified host name of that virtual host. You can set the jvmRoute direct or with the System.property jvmRoute .
• StandardContextValve: Valve that implements the default basic behavior for the StandardContext container implementation. USAGE CONSTRAINT : This implementation is likely to be useful only when processing HTTP requests.
• StandardEngineValve: Valve that implements the default basic behavior for the StandardEngine container implementation. USAGE CONSTRAINT : This implementation is likely to be useful only when processing HTTP requests.
• StandardHostValve: Valve that implements the default basic behavior for the StandardHost container implementation. USAGE CONSTRAINT : This implementation is likely to be useful only when processing HTTP requests.
• ApplicationContext: Standard implementation of ServletContext that represents a web application's execution environment. An instance of this class is associated with each instance of StandardContext .
• StandardWrapper: Standard implementation of the Wrapper interface that represents an individual servlet definition. No child Containers are allowed, and the parent Container must be a Context.
• StandardHost: Standard implementation of the Host interface. Each child container must be a Context implementation to process the requests directed to a particular web application.
• StandardContext: Standard implementation of the Context interface. Each child container must be a Wrapper implementation to process the requests directed to a particular servlet.
• ApplicationFilterConfig: Implementation of a javax.servlet.FilterConfig useful in managing the filter instances instantiated when a web application is first started.
• StandardService: Standard implementation of the Service interface. The associated Container is generally an instance of Engine, but this is not required.
• StandardServer: Standard implementation of the Server interface, available for use (but not required) when deploying and starting Catalina.
• StandardWrapperValve: Valve that implements the default basic behavior for the StandardWrapper container implementation.
• ApplicationContextFacade: Facade object which masks the internal ApplicationContext object from the web application.
• NamingContextListener: Helper class used to initialize and populate the JNDI context associated with each context and server.

Home | Contact Us | Privacy Policy | Terms of Service