Version: 9.4.21.v20190926 |

Automatic Web Application Deployment
Previous | Chapter 4. Deploying to Jetty Home | Next

##### 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 for sponsored feature development

## Automatic Web Application Deployment

The most basic technique for deploying Web Applications is to put a WAR file or Exploded WAR directory into the `${jetty.base}/webapps/` directory and let Jetty’s deployment scanner find it and deploy it under a Context path of the same name.

Only Web Applications that follow the Web Application Layout will be detected by Jetty and deployed this way.

The Context Path assigned to this automatic deployment is based the filename (or directory name) of the WAR.

File or Directory Name | Assigned Context Path
--- | ---
`/webapps/footrope.war` | http://host/footrope/
`/webapps/baggywrinkle-1.0.war` | http://host/baggywrinkle-1.0/
`/webapps/lazaret-2.1.3-SNAPSHOT.war` | http://host/lazaret-2.1.3-SNAPSHOT/
`/webapps/belaying-pins/WEB-INF/web.xml` | http://host/belaying-pins/
`/webapps/root.war` (reserved name) | http://host/
`/webapps/root/WEB-INF/web.xml` (reserved name) | http://host/

Previous | Top | Next
Chapter 4. Deploying to Jetty | Home | Configuring a Specific Web Application Deployment

See an error or something missing? Contribute to this documentation at Github!(Generated: 2019-09-26)