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"
m |
m |
||
| Line 1: | Line 1: | ||
{{Jetty Howto | {{Jetty Howto | ||
| − | |introduction= | + | | introduction= Configuring jetty consists of building a network of connectors and handlers and providing their individual configurations. It is a combination of |
| − | Configuring jetty consists of building a network of connectors and handlers and providing their individual configurations. It is a combination of | + | |
* HTTP server configuration (ports, thread pools, buffers, etc.) | * HTTP server configuration (ports, thread pools, buffers, etc.) | ||
* Web container configuration (webapps deployment, security realms, JNDI etc.) | * Web container configuration (webapps deployment, security realms, JNDI etc.) | ||
* Web application (init parameters, non standard options, etc.) | * Web application (init parameters, non standard options, etc.) | ||
| − | |||
Since Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of components by a variety of techniques: | Since Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of components by a variety of techniques: | ||
* In code | * In code | ||
| Line 16: | Line 14: | ||
* Using Jetty WebApp and Context Deployers | * Using Jetty WebApp and Context Deployers | ||
* Using Web XML Descriptors | * Using Web XML Descriptors | ||
| − | + | }} | |
== In Code == | == In Code == | ||
| Line 48: | Line 46: | ||
== Finally == | == Finally == | ||
| − | Because Jetty configuration can be considered as calling setters on a collection of POJOs, regardless of the actual method used, the [http://download.eclipse.org/jetty/stable-7/apidocs/ apidocs] are the ultimate resource for configuration. | + | Because Jetty configuration can be considered as calling setters on a collection of POJOs, regardless of the actual method used, the [http://download.eclipse.org/jetty/stable-7/apidocs/ apidocs] are the ultimate resource for configuration. |
| − | + | ||
Revision as of 15:40, 11 August 2010
Contents
Introduction
Configuring jetty consists of building a network of connectors and handlers and providing their individual configurations. It is a combination of
- HTTP server configuration (ports, thread pools, buffers, etc.)
- Web container configuration (webapps deployment, security realms, JNDI etc.)
- Web application (init parameters, non standard options, etc.)
Since Jetty components are simply Plain Old Java Objects (POJOs), you can accomplish this assembly and configuration of components by a variety of techniques:
- In code
- Using Jetty XML
- Embedding Jetty
- Using the Jetty Maven Plugin
- Using Your Favorite Dependency Injection Framework
- Configuring Jetty with Spring
- Configuring Jetty with XBean
- Using Jetty WebApp and Context Deployers
- Using Web XML Descriptors
In Code
See the examples in the Jetty 7 Latest Source XRef.
Using Jetty XML
With Jetty XML - dependency injection style XML format. Jetty XML used with jetty.xml and other files
Embedding Jetty
Embedded Jetty.
Using the Jetty Maven Plugin
[[Jetty/Feature/Jetty_Maven_Plugin|Jetty maven plugin]
Using Your Favorite Dependency Injection Framework
Configuring Jetty with Spring
Configuring Jetty with XBean XBean
Using Jetty WebApp and Context Deployers
Using Web XML Descriptors
web.xml descriptors
More
For more configuration references, see the Jetty Configuration Reference pages.
Finally
Because Jetty configuration can be considered as calling setters on a collection of POJOs, regardless of the actual method used, the apidocs are the ultimate resource for configuration.