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"
| Line 5: | Line 5: | ||
| body = | | body = | ||
| − | The documentation for Deployment Manager | + | The documentation for Deployment Manager is forthcoming. |
| more = | | more = | ||
Previously, this feature has been implemented via ContextDeployer. Context Deployer information is still available [[Jetty/Feature/ContextDeployer|here]]. WebApp Deployer information is still available [[Jetty/Feature/WebAppDeployer|here]]. | Previously, this feature has been implemented via ContextDeployer. Context Deployer information is still available [[Jetty/Feature/ContextDeployer|here]]. WebApp Deployer information is still available [[Jetty/Feature/WebAppDeployer|here]]. | ||
}} | }} | ||
Revision as of 16:28, 28 June 2010
Introduction
Jetty provides capability to deploy an arbitrary context or web application by monitoring a directory for changes. If a web application or a context descriptor is added to the directory, a new context will be deployed. If a context descriptor is touched/updated then it's context will be stopped, reconfigured and redeployed. If a context descriptor is removed, then it's context will be stopped and removed from the server.
Feature
The documentation for Deployment Manager is forthcoming.
Additional Resources
Previously, this feature has been implemented via ContextDeployer. Context Deployer information is still available here. WebApp Deployer information is still available here.