Jump to: navigation, search

Jetty/Howto/Configure Jetty

< Jetty‎ | Howto
Revision as of 16:21, 13 August 2010 by Boulay.intalio.com (Talk | contribs)



Introduction

Configuring Jetty consists of building a network of connectors and handlers and providing their individual configurations. It is a combination of

  • HTTP server configuration (ports, thread pools, buffers, etc.)
  • Web container configuration (webapps deployment, security realms, JNDI etc.)
  • Web application (init parameters, non standard options, etc.)

See Jetty Architecture for graphical representations of the interactions among connectors and handlers.

Configuring Jetty

Since Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of Jetty by a variety of techniques:

#IDeveloping Against the Jetty API

#Using Jetty XML

#Embedding Jetty

#Using the Jetty Maven Plugin

#Using Your Favorite Dependency Injection Framework: Spring, XBean

#Using Jetty WebApp and Context Deployers

Developing Against the Jetty API

You can develop both standard web applications and embedded web applications by writing code. The basic approach is to install the required Jetty-7 jars and dependencies on your class path and then write and run a variation of one of the examples in the Embedding Jetty Tutorial.

For more details about setting up your class path, see:

For more information on developing against the Jetty API, as well as explanations of other tools, including the Jetty Maven, Ant, and OSGi plugins, see: How to Develop Jetty.

Above all, study the examples in the Jetty 7 Latest Source XRef.

Using Jetty XML

Jetty XML offers XML equivalents to code. It is based on Java's Reflection API. Classes in the java.lang.reflect represent Java methods and classes, such that you can instantiate objects and invoke their methods based on their names and argument types. Behind the scenes, Jetty's XML config parser translates the XML elements and attributes into Reflection calls.[1]

The default configuration file for Jetty is jetty.xml, typically located at $JETTY_HOME/etc/jetty.xml. Usually jetty.xml configures these components:

  • the Server class (or subclass if extended) and global options
  • a ThreadPool (min & max thread)
  • connectors (ports, timeouts, buffer sizes, protocol, etc.)
  • the handler structure (default handlers and/or a contextHandlerCollections, etc.)
  • the deployment manager that scans for and deploys webapps and contexts
  • login services that provide authentication checking.
  • a request log

Not all Jetty features are configured in jetty.xml. There are several optional configuration files that share the same format as jetty.xml and, if specified, concatenate to it. These configuration files are also stored in $JETTY_HOME/etc/, and examples of them are in svn.

Additional Resources

  1. Ethan McAllum makes this point in his appreciative article about Jetty, What is Jetty

Embedding Jetty

As an alternative to bundling your application as a standard WAR to be deployed in Jetty, you can embed Jetty in your application. When you do so, Jetty is a software component that can be instantiated and used in a Java program just like any POJO. For more information and configuration instructions, see Embedding Jetty.

Using the Jetty Maven Plugin

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. It is an ideal tool to build a web application project, and such projects can use the Jetty Maven Plugin to run the web application in development mode. For information and configuration instructions, see

Using Your Favorite Dependency Injection Framework: Spring, XBean

You can use almost any IoC-style framework, including Spring and XBean, to assemble and configure Jetty.

Configuring Jetty with Spring

The jetty-spring module is included in jetty@codehaus with some convenience classes and a Main method to run Jetty from Spring. For more information, see:

Configuring Jetty with XBean

Using Jetty WebApp and Context Deployers

WebApp and Context Deployers

More

Because Jetty configuration can be considered as calling setters on a collection of POJOs, regardless of the actual method used, the apidocs are the ultimate resource for configuration.