Contact the core Jetty developers at www.webtide.com
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

Deploying Web Applications

Jetty by default includes the etc/jetty-deploy.xml file in start.ini, which configures a web application Deployer that hot deploys files found in the webapps directory. Standard WAR files and jetty configuration files that are placed in the webapps directory will be hot deployed to the server with the following conventions:

If you have a standard web application, it can hot deployed into jetty by copying it into the webapps directory. Alternately to test deployment you can copy the provided test web application provided:

> cp webapps/test.war webapps/myapp.war

The Jetty distribution comes with the following deployed in the webapps directory:

ROOT/

The Jetty welcome page served as static content.

test.xml

The configuration file that deploys the demonstration web application in test.war using the extra configuration contained within test.d

test.war

The demonstration web application that is configured and deployed by test.xml

test.d

A directory containing additional configuration files used by test.xml

async-rest.war

A web application demonstration asynchronous REST to Ebay.

javadoc.xml

A context configuration that deploys as static content the javadoc directory found at jetty.home/javadoc

These demonstration web applications should be removed before using Jetty in production.

See an error or something missing?
Contribute to this documentation at Github!