Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: When the apidocs were split between jetty6 and jetty7 that broke all of the links in this page. I moved all of the links to point to jetty7 (since the link on for jetty6 javadoc is broken too.)


Jetty is configured by dependency injection into the Jetty components. The root component of Jetty is Server, on which you can set an array of Connector instances and an array of Handler instances. Each specific type of connector and handler will have it's own setters and getters for configuration.


  • The JVM will have a single instance of Server
  • The Server will have a single Connector instance, probably a SelectChannelConnector.
  • The Connector will have a port set on it.
  • The Server will have one or more handlers. Typically these will be instances of ContextHandler that wrap other Handler instances for a given context path.
  • The ContextHandler will be configured with a contextPath and wrapped handler for the context.
  • The ContextHandler may be configured with ResourceBase, ClassLoader, VirtualHosts, etc.
  • The ContextHandler may be an instance of WebAppContext which configures itself from the WEB-INF/web.xml file found within the configured ResourceBase and will contain a SessionHandler, which will contain a SecurityHandler, which will container contain a ServletHandler
  • The ContextHandler may contain a ServletHandler, which will contain:

All these components have setters and getters for configuration. These may be configured by:


Contact the core Jetty developers at
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery