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

Quick Search    Search Deep

org.apache.ajp.test.* (2)org.apache.ajp.tomcat33.* (1)org.apache.ajp.tomcat4.* (13)
org.apache.ajp.tomcat4.config.* (4)

org.apache.ajp: Javadoc index of package org.apache.ajp.


Package Samples:

org.apache.ajp.tomcat33
org.apache.ajp.tomcat4.config
org.apache.ajp.tomcat4
org.apache.ajp.test

Classes:

NSConfig: Generates automatic Netscape nsapi_redirect configurations based on the Tomcat server.xml settings and the war contexts initialized during startup. This config interceptor is enabled by inserting an NSConfig element in the <ContextManager> tag body inside the server.xml file like so: ... NSConfig options /> ... where options can include any of the following attributes: configHome - default parent directory for the following paths. If not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following paths is absolute. objConfig - path to use for writing Netscape obj.conf file. If ...
IISConfig: Generates automatic IIS isapi_redirect configurations based on the Tomcat server.xml settings and the war contexts initialized during startup. This config interceptor is enabled by inserting an IISConfig element in the <ContextManager> tag body inside the server.xml file like so: ... IISConfig options /> ... where options can include any of the following attributes: configHome - default parent directory for the following paths. If not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following paths is absolute. regConfig - path to use for writing IIS isapi_redirect registry ...
ApacheConfig: Generates automatic apache mod_jk configurations based on the Tomcat server.xml settings and the war contexts initialized during startup. This config interceptor is enabled by inserting an ApacheConfig Listener in the server.xml file like so: ... org.apache.ajp.tomcat4.config.ApacheConfig options /> ... where options can include any of the following attributes: configHome - default parent directory for the following paths. If not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following paths is absolute. jkConfig - path to use for writing Apache mod_jk conf file. If not set, defaults ...
BaseJkConfig: Base class for automatic jk based configurations based on the Tomcat server.xml settings and the war contexts initialized during startup. This config interceptor is enabled by inserting a Config element in the <ContextManager> tag body inside the server.xml file like so: ... ???Config options /> ... where options can include any of the following attributes: configHome - default parent directory for the following paths. If not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following paths is absolute. workersConfig - path to workers.properties file used by jk connector. If ...
RequestHandler: Handle messages related with basic request information. This object can handle the following incoming messages: - "FORWARD_REQUEST" input message ( sent when a request is passed from the web server ) - "PING REQUEST" input message (sent by the web server to determine if tomcat is not frozen, a PONG REPLY will be sent back) - "RECEIVE_BODY_CHUNK" input ( sent by container to pass more body, in response to GET_BODY_CHUNK ) It can handle the following outgoing messages: - SEND_HEADERS. Pass the status code and headers. - SEND_BODY_CHUNK. Send a chunk of body - GET_BODY_CHUNK. Request a chunk of body ...
Ajp13: Represents a single, persistent connection between the web server and the servlet container. Uses the Apache JServ Protocol version 1.3 for communication. Because this protocal does not multiplex requests, this connection can only be associated with a single request-handling cycle at a time. This class contains knowledge about how an individual packet is laid out (via the Ajp13Packet class), and also about the stages of communicaton between the server and the servlet container. It translates from Tomcat's internal servlet support methods (e.g. doWrite) to the correct packets to send to the web ...
AjpHandler: Base class for handlers of Ajp messages. Jk provide a simple bidirectional communication mechanism between the web server and a servlet container. It is based on messages that are passed between the 2 server, using a single thread on each side. The container side must be able to deal with at least the "REQUEST FORWARD", the server side must be able to deal with at least "HEADERS", "BODY", "END" messages.
Ajp13Packet: A single packet for communication between the web server and the container. Designed to be reused many times with no creation of garbage. Understands the format of data types for these packets. Can be used (somewhat confusingly) for both incoming and outgoing packets. See Ajp14/Ajp13Packet.
Logger: A simple logger class used by classes in this package. The intention is for this class to be overridden so that log messages from classes in this package can be adapted to loggers used by the connector implementations for various servlet containers.
Ajp14Interceptor: Tomcat 33 module implementing the Ajp14 protocol. The actual protocol implementation is in Ajp14.java, this is just an adapter to plug it into tomcat.
NegociationHandler: Handler for the protocol negotiation. It will authenticate and exchange information about supported messages on each end.
Ajp13Connector: Implementation of an Ajp13 connector.
JkServlet: Module loader for JkServlet
TestAjp13
Ajp13Server
TestAll
Ajp14Request
Ajp14Response
Ajp13InputStream
Ajp13Logger
Ajp13OutputStream
Ajp13Processor
Ajp13Request

Home | Contact Us | Privacy Policy | Terms of Service