Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Howto/Deploy Web Applications"
| Line 4: | Line 4: | ||
=== Webapps Deployment === | === Webapps Deployment === | ||
The $JETTY_HOME/webapps directory is scanned at startup for webapplications to deploy: | The $JETTY_HOME/webapps directory is scanned at startup for webapplications to deploy: | ||
| − | * | + | * The file foo.war will be deployed as a webapp at context /foo |
| − | * | + | * The directory foo/ will be deployed at context /foo. If the directory has a WEB-INF subdirectory, it will be treated as servlet webapp, otherwise it will served only as static content. |
* If both a foo.war and a foo/ directory exists, then the one with the most recent last-modified date is used. | * If both a foo.war and a foo/ directory exists, then the one with the most recent last-modified date is used. | ||
* If the webapp is called root.war or the directory is called root/ then it will be deployed at the / context. | * If the webapp is called root.war or the directory is called root/ then it will be deployed at the / context. | ||
Revision as of 21:15, 4 February 2010
Introduction
Jetty can deploy web applications as war files (packed or unpacked), as provided or with overridden configuration, with static or hot deployment.
Steps
Webapps Deployment
The $JETTY_HOME/webapps directory is scanned at startup for webapplications to deploy:
- The file foo.war will be deployed as a webapp at context /foo
- The directory foo/ will be deployed at context /foo. If the directory has a WEB-INF subdirectory, it will be treated as servlet webapp, otherwise it will served only as static content.
- If both a foo.war and a foo/ directory exists, then the one with the most recent last-modified date is used.
- If the webapp is called root.war or the directory is called root/ then it will be deployed at the / context.