Home >> All >> org >> mortbay >> [ jetty Javadoc ]

•	org.mortbay.jetty.jmx.* (1)	•	org.mortbay.jetty.plus.* (8)	•	org.mortbay.jetty.servlet.* (32)
•	org.mortbay.jetty.servlet.jmx.* (10)	•	org.mortbay.jetty.win32.* (1)

• org.mortbay.jetty: Javadoc index of package org.mortbay.jetty.


Package Samples:

• org.mortbay.jetty.jmx
• org.mortbay.jetty.servlet
• org.mortbay.jetty.servlet.jmx
• org.mortbay.jetty.win32
• org.mortbay.jetty.plus

Classes:

• Default: The default servlet. This servlet, normally mapped to /, provides the handling for static content, OPTION and TRACE methods for the context. The following initParameters are supported: acceptRanges If true, range requests and responses are supported dirAllowed If true, directory listings are returned if no welcome file is found. Else 403 Forbidden. putAllowed If true, the PUT method is allowed delAllowed If true, the DELETE method is allowed redirectWelcome If true, welcome files are redirected rather than forwarded to. minGzipLength If set to a positive integer, then static content larger than ...
• Invoker: Dynamic Servlet Invoker. This servlet invokes anonymous servlets that have not been defined in the web.xml or by other means. The first element of the pathInfo of a request passed to the envoker is treated as a servlet name for an existing servlet, or as a class name of a new servlet. This servlet is normally mapped to /servlet/* This servlet support the following initParams: nonContextServlets If false, the invoker can only load servlets from the contexts classloader. This is false by default and setting this to true may have security implications. verbose If true, log dynamic loads * All other ...
• Server: The Jetty HttpServer. This specialization of org.mortbay.http.HttpServer adds knowledge about servlets and their specialized contexts. It also included support for initialization from xml configuration files that follow the XmlConfiguration dtd. HttpContexts created by Server are of the type org.mortbay.jetty.servlet.ServletHttpContext unless otherwise specified. This class also provides a main() method which starts a server for each config file passed on the command line. If the system property JETTY_NO_SHUTDOWN_HOOK is not set to true, then a shutdown hook is thread is registered to stop these ...
• AbstractSessionManager: An Abstract implementation of SessionManager. The partial implementation of SessionManager interface provides the majority of the handling required to implement a SessionManager. Concrete implementations of SessionManager based on AbstractSessionManager need only implement the newSession method to return a specialized version of the Session inner class that provides an attribute Map. If the property org.mortbay.jetty.servlet.AbstractSessionManager.23Notifications is set to true, the 2.3 servlet spec notification style will be used.
• ServletHandler: Servlet HttpHandler. This handler maps requests to servlets that implement the javax.servlet.http.HttpServlet API. This handler does not implement the full J2EE features and is intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported. If a SessionManager is not added to the handler before it is initialized, then a HashSessionManager with a standard java.util.Random generator is created.
• WebApplicationContext: Standard web.xml configured HttpContext. This specialization of HttpContext uses the standardized web.xml to describe a web application and configure the handlers for the HttpContext. If a file named web-jetty.xml or jetty-web.xml is found in the WEB-INF directory it is applied to the context using the XmlConfiguration format. A single WebApplicationHandler instance is used to provide security, filter, sevlet and resource handling.
• Service: Run Jetty as a Win32 service. System.out and System.err output can be controlled with java properties: SERVICE_OUT and SERVICE_ERR. The log file can be controlled with the property SERVICE_LOG_FILE Example jettysvc -c -DSERVICE_OUT="./logs/jettysvc.out" \\ -DSERVICE_ERR="./logs/jettysvc.err" \\ Jetty.xml wrkdir=$JETTY_HOME
• ServletHttpRequest: Servlet Request Wrapper. This class wraps a Jetty HTTP request as a 2.2 Servlet request. Note that this wrapper is not synchronized and if a request is to be operated on by multiple threads, then higher level synchronizations may be required.
• ServletHttpResponse: Servlet Response Wrapper. This class wraps a Jetty HTTP response as a 2.2 Servlet response. Note that this wrapper is not synchronized and if a response is to be operated on by multiple threads, then higher level synchronizations may be required.
• ServerMBean: JettyServer MBean. This Model MBean class provides the mapping for HttpServer management methods. It also registers itself as a membership listener of the HttpServer, so it can create and destroy MBean wrappers for listeners and contexts.
• ServletHolder: Servlet Instance and Context Holder. Holds the name, params and some state of a javax.servlet.Servlet instance. It implements the ServletConfig interface. This class will organise the loading of the servlet when needed or requested.
• RequestListenerFilter: Request Listener Filter. This filter is automatically inserted by WebApplicationHandler when ServletRequestListener or ServletRequestAttributeListeners event listeners are registered with the context.
• FormAuthenticator: FORM Authentication Authenticator. The HTTP Session is used to store the authentication status of the user, which can be distributed. If the realm implements SSORealm, SSO is supported.
• ServletSSL: Jetty Servlet SSL support utilities. A collection of utilities required to support the SSL requirements of the Servlet 2.2 and 2.3 specs. Used by the SSL listener classes.
• TMService: A TMService represents a JTA Service and is used to acces JTA main interfaces ( UserTransaction and TransactionManager ).
• WebApplicationHandler: WebApp HttpHandler. This handler extends the ServletHandler with security, filter and resource capabilities to provide full J2EE web container support.
• ServletHttpContextMBean: Web Application MBean. Note that while Web Applications are HttpContexts, the MBean is not derived from HttpContextMBean as they are managed differently.
• WebApplicationMBean: Web Application MBean. Note that while Web Applications are HttpContexts, the MBean is not derived from HttpContextMBean as they are managed differently.
• WebApplicationContextMBean: Web Application MBean. Note that while Web Applications are HttpContexts, the MBean is not derived from HttpContextMBean as they are managed differently.
• ServletHttpContext: ServletHttpContext. Extends HttpContext with conveniance methods for adding servlets. Enforces a single ServletHandler per context.
• Server: The Jetty HttpServer. This specialization of org.mortbay.jetty.Server adds knowledge about JNDI and Transaction Management
• ServletWriter: Servlet PrintWriter. This writer can be disabled. It is crying out for optimization.
• SessionManager: Session Manager. The API required to manage sessions for a servlet context.
• JotmService: Implementation of TMService for Objectweb JOTM (www.objectweb.org)

Home | Contact Us | Privacy Policy | Terms of Service