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/Howto/Configure Jetty"
| Line 9: | Line 9: | ||
* Use the [[Jetty/Feature/Jetty_Maven_Plugin|jetty-maven-plugin]] | * Use the [[Jetty/Feature/Jetty_Maven_Plugin|jetty-maven-plugin]] | ||
| − | Web applications (aka WARs, webapps and contexts) can be configured either with standard based web.xml, annotations | + | Web applications (aka WARs, webapps and contexts) can be configured either with standard based web.xml, annotations, by calling the jetty API directly (as above) or with a combination of approaches. |
| + | |||
| + | See the [[Jetty/Reference#Configuration|Jetty Configuration Reference]] pages. | ||
|steps= | |steps= | ||
| + | |||
}} | }} | ||
Revision as of 05:57, 18 September 2009
Introduction
Jetty configuration is a combination of configuration of the HTTP server, the web container and the web application.
Jetty itself is a collection of Plain Old Java Objects (POJOs) and can be configured in several ways:
- Calling the API from a java program (see the Embedding Jetty Tutorial).
- Calling the API from jetty XML (see XML syntax reference and jetty.xml reference).
- Assemble POJOs from Spring (see the File Server with spring example).
- Use the jetty-maven-plugin
Web applications (aka WARs, webapps and contexts) can be configured either with standard based web.xml, annotations, by calling the jetty API directly (as above) or with a combination of approaches.
See the Jetty Configuration Reference pages.