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 1: | Line 1: | ||
{{Jetty Feature | {{Jetty Feature | ||
| − | | introduction = | + | | introduction = Jetty provides capability to deploy an arbitrary context or web application with Jetty-specific configuration. This capability is implemented via ContextDeployer mechanism. |
| − | | body = | + | | body = The ContextDeployer is typically defined in Jetty configuration file. It will scan a directory that contains xml descriptors that define contexts at a configured interval. Te |
| more = (optional) - links, additional references | | more = (optional) - links, additional references | ||
| category = [[Category:Jetty Feature]] | | category = [[Category:Jetty Feature]] | ||
}} | }} | ||
Revision as of 09:59, 4 February 2010
Introduction
Jetty provides capability to deploy an arbitrary context or web application with Jetty-specific configuration. This capability is implemented via ContextDeployer mechanism.
Feature
The ContextDeployer is typically defined in Jetty configuration file. It will scan a directory that contains xml descriptors that define contexts at a configured interval. Te
Additional Resources
(optional) - links, additional references