Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Feature/Hot Deployment"
m |
m |
||
| Line 7: | Line 7: | ||
If the scan interval is zero, then the directory is only scanned at startup. | If the scan interval is zero, then the directory is only scanned at startup. | ||
| − | To statically deploy only standard web applications at startup, use the [[ | + | To statically deploy only standard web applications at startup, use the [[Jetty/Feature/WebAppDeployer|WebApp Deployer]]. |
| category = [[Category:Jetty Feature]] | | category = [[Category:Jetty Feature]] | ||
}} | }} | ||
Revision as of 20:03, 18 June 2010
Introduction
Jetty provides capability to deploy an arbitrary context or web application by monitoring a configuration directory for changes to the deployment descriptors. If a descriptor is added to the directory, a new context will be deployed. If a descriptor is touched/updated then it's context will be stopped, reconfigured and redeployed. If a descriptor is removed, then it's context will be stopped and removed from the server. This capability is implemented via Context Deployer mechanism.
Feature
The Context Deployer may be used to (hot)deploy an arbitrary Context or Web Application with Jetty specific configuration. The deployment descriptors are in jetty xml format and define and configure individual contexts. If the scan interval is non-zero, the configuration directory is scanned at that interval (in seconds) for changes to the deployment descriptors. If the scan interval is zero, then the directory is only scanned at startup.
To statically deploy only standard web applications at startup, use the WebApp Deployer.