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
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 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), then the context path
is /. If example.war and
example/ exist, then 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, then 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.
Alternately, to test deployment you can copy the 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.xmlThe configuration file that deploys the demonstration web
application in test.war using the extra
configuration contained within test.d
test.warThe demonstration web application that is configured and
deployed by test.xml
test.dA directory containing additional configuration files used by
test.xml
async-rest.warA web application demonstration of asynchronous REST to eBay.
javadoc.xmlA context configuration that deploys as static content the
javadoc directory found at
$jetty.home/javadoc
You should remove these demonstration web applications before using Jetty in production.
See an error or something missing? Contribute to this documentation at Github!