Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Reference/Jetty Architecture"
(27 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=Jetty 7 Architecture= | =Jetty 7 Architecture= | ||
+ | |||
+ | {{Jetty Redirect|http://www.eclipse.org/jetty/documentation/current/basic-architecture.html}} | ||
==View from 20,000 feet== | ==View from 20,000 feet== | ||
Line 7: | Line 9: | ||
The Jetty [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Server.html Server] is the plumbing between a collection of [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Connector.html Connectors] that accept [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/HttpConnection.html HTTP connections], and a collection of [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Handler.html Handlers] that service [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Request.html requests] from the connections and produce [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Response.html responses], with the work being done by threads taken from a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/thread/ThreadPool.html thread pool]. | The Jetty [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Server.html Server] is the plumbing between a collection of [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Connector.html Connectors] that accept [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/HttpConnection.html HTTP connections], and a collection of [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Handler.html Handlers] that service [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Request.html requests] from the connections and produce [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Response.html responses], with the work being done by threads taken from a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/thread/ThreadPool.html thread pool]. | ||
− | |||
− | {| | + | {{note|While the jetty request/responses are derived from the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/servlet/package-summary.html Servlet API], the full features of the servlet API are only available if the appropriate handlers are configured. For example, the session API on the request is inactive unless the request has been passed to a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/session/SessionHandler.html Session Handler]. The concept of a Servlet itself is implemented by a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html Servlet Handler]. If servlets are not required, there is very little overhead in the use of the servlet request/response APIs. Thus you can build a Jetty server using only connectors and handlers, without using Servlets.}} |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | While the jetty request/responses are derived from the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/servlet/package-summary.html Servlet API], the full features of the servlet API are only available if the appropriate handlers are configured. For example, the session API on the request is inactive unless the request has been passed to a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/session/SessionHandler.html Session Handler]. The concept of a Servlet itself is implemented by a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html Servlet Handler]. If servlets are not required, there is very little overhead in the use of the servlet request/response APIs. | + | |
− | |||
− | |||
− | + | The job of configuring jetty is the job of building a network of connectors and handlers and providing their individual configurations. As Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of components by a variety of techniques: | |
− | + | * In code. See the examples in the [http://download.eclipse.org/jetty/stable-7/xref/ Jetty 7 Latest Source XRef]. | |
− | + | * With [http://wiki.eclipse.org/Jetty/Reference/jetty.xml_usage Jetty XML] - dependency injection style XML format. | |
− | * In code. See the examples in the [http://download.eclipse.org/jetty/stable-7/xref/ | + | * With your dependency injection framework of choice: [http://www.springsource.org/ Spring] or [http://geronimo.apache.org/xbean/index.html XBean]. |
− | * With [/ | + | * Using Jetty [http://wiki.eclipse.org/Jetty/Howto/Deploy_Web_Applications WebApp and Context Deployers]. |
− | * With your dependency injection framework of choice: [Spring] or [XBean] | + | |
− | * | + | |
==Patterns== | ==Patterns== | ||
Line 36: | Line 28: | ||
The JSR77 inspired life cycle of most jetty components is represented by [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/component/LifeCycle.html LifeCycle] interface and the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/component/AbstractLifeCycle.html AbstractLifeCycle] implementation used as the base of many Jetty components. | The JSR77 inspired life cycle of most jetty components is represented by [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/component/LifeCycle.html LifeCycle] interface and the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/component/AbstractLifeCycle.html AbstractLifeCycle] implementation used as the base of many Jetty components. | ||
− | Jetty provides | + | Jetty provides its own [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/io/package-summary.html IO Buffering] abstract over String, byte arrays and NIO buffers. This allows for greater portability of Jetty as well as hiding some of the complexity of the NIO layer and its advanced features. |
==Connectors== | ==Connectors== | ||
Line 42: | Line 34: | ||
[[Image:JettyUML3.png]] | [[Image:JettyUML3.png]] | ||
− | |||
− | {| | + | {{note|This diagram is a little out of date, as a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/io/Connection.html Connection] interface has been extracted out of HttpConnector to allow support for the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/ajp/package-summary.html AJP protocol].}} |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | This diagram is a little out of date, as a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/io/Connection.html Connection] interface has been extracted out of HttpConnector to allow support for the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/ajp/package-summary.html AJP protocol]. | + | |
− | + | ||
− | |||
− | The connectors represent the protocol handlers that accept connections, parse requests and generate responses. The different types of connectors available are based on the protocols , scheduling model and IO APIs used: | + | The connectors represent the protocol handlers that accept connections, parse requests and generate responses. The different types of connectors available are based on the protocols, scheduling model and IO APIs used: |
− | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/bio/SocketConnector.html SocketConnector] - for few busy connections or when NIO is not available | + | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/bio/SocketConnector.html SocketConnector] - for few busy connections or when NIO is not available |
* [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/nio/BlockingChannelConnector.html BlockingChannelConnector] - for few busy connections when NIO is available | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/nio/BlockingChannelConnector.html BlockingChannelConnector] - for few busy connections when NIO is available | ||
− | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/nio/SelectChannelConnector.html SelectChannelConnector] - for many mostly idle connections or asynchronous handling of Ajax requests | + | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/nio/SelectChannelConnector.html SelectChannelConnector] - for many mostly idle connections or asynchronous handling of Ajax requests |
* [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/ssl/SslSocketConnector.html SslSocketConnector] - SSL without NIO | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/ssl/SslSocketConnector.html SslSocketConnector] - SSL without NIO | ||
− | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/ssl/SslSelectChannelConnector.html SslSelectChannelConnector] - SSL with non blocking NIO support | + | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/ssl/SslSelectChannelConnector.html SslSelectChannelConnector] - SSL with non blocking NIO support |
* [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/ajp/Ajp13SocketConnector.html AJPConnector] AJP protocol support for connections from apache mod_jk or mod_proxy_ajp | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/ajp/Ajp13SocketConnector.html AJPConnector] AJP protocol support for connections from apache mod_jk or mod_proxy_ajp | ||
Line 67: | Line 51: | ||
[[Image:JettyUML4.png]] | [[Image:JettyUML4.png]] | ||
− | The [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Handler.html] is the component that deals with received requests. The core API of a handler is the handle method: | + | The [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Handler.html Handler] is the component that deals with received requests. The core API of a handler is the handle method: |
− | < | + | <source lang="java"> |
− | + | public void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) | |
− | + | throws IOException, ServletException | |
− | </ | + | </source> |
− | An implementation of this method | + | Parameters: |
+ | |||
+ | * <tt>target</tt>–The target of the request, either a URI or a name. | ||
+ | * <tt>baseRequest</tt>–The original unwrapped request object. | ||
+ | * <tt>request</tt>–The request either as the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Request.html Request] object or a wrapper of that request. You can use the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/HttpConnection.html HttpConnection.getCurrentConnection()] method to access the Request object if required. | ||
+ | * <tt>response</tt>–The response as the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/Response.html Response] object or a wrapper of that request. You can use the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/HttpConnection.html HttpConnection.getCurrentConnection()] method to access the Response object if required. | ||
+ | |||
+ | An implementation of this method can handle the request, pass the request onto another handler (or servlet) or it might modify and/or wrap the request and then pass it on. This gives three styles of Handler: <br class="atl-forced-newline" /> | ||
# Coordinating Handlers - Handlers that route requests to other handlers (eg [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerCollection.html HandlerCollection], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandlerCollection.html ContextHandlerCollection]) | # Coordinating Handlers - Handlers that route requests to other handlers (eg [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerCollection.html HandlerCollection], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandlerCollection.html ContextHandlerCollection]) | ||
# Filtering Handlers - Handlers that augment a request and pass it on to other handlers (eg. [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerWrapper.html HandlerWrapper], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html ContextHandler], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/session/SessionHandler.html SessionHandler]) | # Filtering Handlers - Handlers that augment a request and pass it on to other handlers (eg. [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerWrapper.html HandlerWrapper], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html ContextHandler], [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/session/SessionHandler.html SessionHandler]) | ||
# Generating Handlers - Handlers that produce content (eg [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ResourceHandler.html ResourceHandler] and [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html ServletHandler]) | # Generating Handlers - Handlers that produce content (eg [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ResourceHandler.html ResourceHandler] and [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html ServletHandler]) | ||
+ | |||
+ | ===Nested Handlers and Handlers Called Sequentially=== | ||
+ | |||
+ | You can combine handlers to handle different aspects of a request by nesting them, calling them in sequence, or by combining the two models. | ||
+ | |||
+ | [[Image:Jettynested.png]] | ||
+ | |||
+ | * Handlers called in sequence perform actions that do not depend on the next invocation, nor on the handler order. They handle a request and generate the response without interacting with other handlers. The main class for this model is [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerCollection.html Handler Collection]. | ||
+ | * Nested handlers are called according to a before/invokeNext/after pattern. The main class for nested handlers is [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/HandlerWrapper.html Handler Wrapper]. Nested handlers are much more common than those called in sequence. | ||
See also [http://wiki.eclipse.org/Jetty/Howto/Write_Jetty_Handler Writing a Jetty Handler]. | See also [http://wiki.eclipse.org/Jetty/Howto/Write_Jetty_Handler Writing a Jetty Handler]. | ||
Line 88: | Line 88: | ||
[[Image:JettyUML5.png]] | [[Image:JettyUML5.png]] | ||
− | The [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html ServletHandler] is a Handler that generates content by passing the request to any configured [http:// | + | The [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHandler.html ServletHandler] is a Handler that generates content by passing the request to any configured [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/FilterHolder.html Filter]s and then to a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletHolder.html Servlet] mapped by a URI pattern. |
A ServletHandler is normally deployed within the scope of a servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html Context], which is a ContextHandler that provides convenience methods for mapping URIs to servlets. | A ServletHandler is normally deployed within the scope of a servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html Context], which is a ContextHandler that provides convenience methods for mapping URIs to servlets. | ||
− | Filters and Servlets | + | Filters and Servlets can also use a [http://download.oracle.com/docs/cd/E17477_01/javaee/5/api/javax/servlet/RequestDispatcher.html RequestDispatcher] to reroute a request to another context or another servlet in the current context. |
==Context== | ==Context== | ||
− | Contexts are handlers that group other handlers below a particular URI context path or a virtual host. Typcially a context | + | Contexts are handlers that group other handlers below a particular URI context path or a virtual host. Typcially a context can have : |
* A context path that defines which requests are handled by the context (eg /myapp ) | * A context path that defines which requests are handled by the context (eg /myapp ) | ||
Line 107: | Line 107: | ||
* [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html ContextHandler] | * [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/server/handler/ContextHandler.html ContextHandler] | ||
* Servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletContextHandler.html Context] | * Servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletContextHandler.html Context] | ||
− | * or a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/WebAppContext. | + | * or a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/WebAppContext.html Web Application Context] |
A web application context combines handlers for security, session and servlets in a single unit that can be configured with a web.xml descriptor. | A web application context combines handlers for security, session and servlets in a single unit that can be configured with a web.xml descriptor. | ||
Line 117: | Line 117: | ||
A [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/WebAppContext.html Web App Context] is a derivation of the servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletContextHandler.html Context] that supports the standardized layout of a web application and configuration of session, security, listeners, filter, servlets and JSP via a web.xml descriptor normally found in the WEB-INF directory of a webapplication. | A [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/WebAppContext.html Web App Context] is a derivation of the servlet [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/servlet/ServletContextHandler.html Context] that supports the standardized layout of a web application and configuration of session, security, listeners, filter, servlets and JSP via a web.xml descriptor normally found in the WEB-INF directory of a webapplication. | ||
− | Essentially the WebAppContext is a convenience class | + | Essentially the WebAppContext is a convenience class that assists the construction and configuration of other handlers to achieve a standard web application configuration. |
− | Configuration is actually done by pluggable implementations of the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/Configuration.html Configuration] class and the prime among these is [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/JettyWebXmlConfiguration.html WebXmlConfiguration] | + | Configuration is actually done by pluggable implementations of the [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/Configuration.html Configuration] class and the prime among these is [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/webapp/JettyWebXmlConfiguration.html WebXmlConfiguration]. |
Latest revision as of 15:38, 23 April 2013
Contents
Jetty 7 Architecture
View from 20,000 feet
The Jetty Server is the plumbing between a collection of Connectors that accept HTTP connections, and a collection of Handlers that service requests from the connections and produce responses, with the work being done by threads taken from a thread pool.
The job of configuring jetty is the job of building a network of connectors and handlers and providing their individual configurations. As Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of components by a variety of techniques:
- In code. See the examples in the Jetty 7 Latest Source XRef.
- With Jetty XML - dependency injection style XML format.
- With your dependency injection framework of choice: Spring or XBean.
- Using Jetty WebApp and Context Deployers.
Patterns
The implementation of Jetty follows some fairly standard patterns. Most abstract concepts such as Connector, Handler and Buffer are captured by interfaces. Generic handling for those interfaces is then provided in an Abstract implementation such as AbstractConnector, AbstractHandler and AbstractBuffer.
The JSR77 inspired life cycle of most jetty components is represented by LifeCycle interface and the AbstractLifeCycle implementation used as the base of many Jetty components.
Jetty provides its own IO Buffering abstract over String, byte arrays and NIO buffers. This allows for greater portability of Jetty as well as hiding some of the complexity of the NIO layer and its advanced features.
Connectors
The connectors represent the protocol handlers that accept connections, parse requests and generate responses. The different types of connectors available are based on the protocols, scheduling model and IO APIs used:
- SocketConnector - for few busy connections or when NIO is not available
- BlockingChannelConnector - for few busy connections when NIO is available
- SelectChannelConnector - for many mostly idle connections or asynchronous handling of Ajax requests
- SslSocketConnector - SSL without NIO
- SslSelectChannelConnector - SSL with non blocking NIO support
- AJPConnector AJP protocol support for connections from apache mod_jk or mod_proxy_ajp
Handlers
The Handler is the component that deals with received requests. The core API of a handler is the handle method:
public void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException
Parameters:
- target–The target of the request, either a URI or a name.
- baseRequest–The original unwrapped request object.
- request–The request either as the Request object or a wrapper of that request. You can use the HttpConnection.getCurrentConnection() method to access the Request object if required.
- response–The response as the Response object or a wrapper of that request. You can use the HttpConnection.getCurrentConnection() method to access the Response object if required.
An implementation of this method can handle the request, pass the request onto another handler (or servlet) or it might modify and/or wrap the request and then pass it on. This gives three styles of Handler:
- Coordinating Handlers - Handlers that route requests to other handlers (eg HandlerCollection, ContextHandlerCollection)
- Filtering Handlers - Handlers that augment a request and pass it on to other handlers (eg. HandlerWrapper, ContextHandler, SessionHandler)
- Generating Handlers - Handlers that produce content (eg ResourceHandler and ServletHandler)
Nested Handlers and Handlers Called Sequentially
You can combine handlers to handle different aspects of a request by nesting them, calling them in sequence, or by combining the two models.
- Handlers called in sequence perform actions that do not depend on the next invocation, nor on the handler order. They handle a request and generate the response without interacting with other handlers. The main class for this model is Handler Collection.
- Nested handlers are called according to a before/invokeNext/after pattern. The main class for nested handlers is Handler Wrapper. Nested handlers are much more common than those called in sequence.
See also Writing a Jetty Handler.
Servlets
The ServletHandler is a Handler that generates content by passing the request to any configured Filters and then to a Servlet mapped by a URI pattern.
A ServletHandler is normally deployed within the scope of a servlet Context, which is a ContextHandler that provides convenience methods for mapping URIs to servlets.
Filters and Servlets can also use a RequestDispatcher to reroute a request to another context or another servlet in the current context.
Context
Contexts are handlers that group other handlers below a particular URI context path or a virtual host. Typcially a context can have :
- A context path that defines which requests are handled by the context (eg /myapp )
- A resource base for static content (a docroot)
- A class loader to obtain classes specific to the context (typically docroot/WEB-INF/classes)
- Virtual host names
Contexts implementations include:
- ContextHandler
- Servlet Context
- or a Web Application Context
A web application context combines handlers for security, session and servlets in a single unit that can be configured with a web.xml descriptor.
Web Applications
A Web App Context is a derivation of the servlet Context that supports the standardized layout of a web application and configuration of session, security, listeners, filter, servlets and JSP via a web.xml descriptor normally found in the WEB-INF directory of a webapplication.
Essentially the WebAppContext is a convenience class that assists the construction and configuration of other handlers to achieve a standard web application configuration.
Configuration is actually done by pluggable implementations of the Configuration class and the prime among these is WebXmlConfiguration.