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 server instances that configure the deploy module will have a
web application deployer that hot deploys files found in the
webapps directory. Standard WAR files and jetty configuration
files that you place in the webapps directory are hot
deployed to the server with the following conventions:

A directory called example/ is deployed as a
standard web application if it contains a WEB-INF/
subdirectory, otherwise it is deployed as context of static content. The
context path is /example (that is,
http://localhost:8080/example/) unless the base
name is ROOT (case insensitive), in which case the context path is /. If
the directory name ends with ".d" it is ignored (but may be used by
explicit configuration).

A file called example.war is deployed as a
standard web application with the context path
/example (that is,
http://localhost:8080/example/). If the base name
is ROOT (case insensitive), the context path is /.
If example.war and example/
exist, only the WAR is deployed (which may use the directory as an
unpack location).

An XML file like example.xml is deployed as a
context whose configuration is defined by the XML. The configuration
itself must set the context path. If example.xml
and example.war exist, only the XML is deployed
(which may use the WAR in its configuration).

If you have a standard web application, you can hot deploy it into
Jetty by copying it into the webapps directory.

Jetty Demonstration Web Applications

The demo-base/webapps directory contains the following deployable
and auxiliary files:

ROOT/

A directory of static content that is deployed to the root
context / due to it's name. Contains the Jetty demo welcome
page.

test.xml

A context configuration file that configures and deploys
test.war. The additional configuration includes
the context path as well as setting additional descriptors found in
the test.d directory.

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 to inject extra configuration into
test.war.

async-rest.war

A web application demonstration of asynchronous REST to eBay,
automatically deployed to /async-rest based on the file name.