Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Reference/jetty.xml usage"
(New page: {{Jetty Reference | introduction = xxx | body = }}) |
|||
Line 3: | Line 3: | ||
| body = | | body = | ||
}} | }} | ||
+ | |||
+ | |||
+ | == Using <tt>jetty.xml</tt> == | ||
+ | |||
+ | To use <tt>jetty.xml</tt>, specify it as a configuration file when running Jetty. | ||
+ | |||
+ | java -jar start.jar etc/jetty.xml | ||
+ | |||
+ | {{note|Configuration files|If you start up Jetty without specifying a configuration file, Jetty will automatically locate and use the default installation jetty.xml file. Therefore <tt>java -jar start.jar</tt> is equivalent to <tt>java -jar start.jar etc/jetty.xml</tt>.}} | ||
+ | |||
+ | == Multiple Configuration Files == | ||
+ | |||
+ | You are not limited to one configuration file; you may use multiple configuration files when running Jetty, and Jetty will configure the appropriate server instance. | ||
+ | |||
+ | The id of the server in the <code><Configure></code> tag specifies which instance you wish to configure. Each server id in a configuration file creates a new Server instance within the same JVM. If the same id is used across multiple configuration files, those configurations are all applied to the same server. | ||
+ | |||
+ | == Parameterizing Configuration Files == | ||
+ | |||
+ | The configuration files may be parameterized with either system properties (using <code><SystemProperty></code>) or properties files (using <code><Property></code>) passed via the command line. For example, this code in <tt>jetty.xml</tt> allows the port to be defined on the command line, falling back onto <var>8080</var> if the port was not specified: | ||
+ | |||
+ | <source lang="xml"> | ||
+ | <Set name="port"><SystemProperty name="jetty.port" default="8080"/></Set> | ||
+ | </source> | ||
+ | |||
+ | Then you modify the port while running Jetty by using this command: | ||
+ | java -Djetty.port=8888 -jar start.jar etc/jetty.xml | ||
+ | |||
+ | An example of defining both system properties and properties files from the command line: | ||
+ | java -Djetty.port=8888 -jar start.jar myjetty.properties etc/jetty.xml etc/other.xml |
Revision as of 01:02, 8 February 2010
Contents
Introduction
xxx
Using jetty.xml
To use jetty.xml, specify it as a configuration file when running Jetty.
java -jar start.jar etc/jetty.xml
Multiple Configuration Files
You are not limited to one configuration file; you may use multiple configuration files when running Jetty, and Jetty will configure the appropriate server instance.
The id of the server in the <Configure>
tag specifies which instance you wish to configure. Each server id in a configuration file creates a new Server instance within the same JVM. If the same id is used across multiple configuration files, those configurations are all applied to the same server.
Parameterizing Configuration Files
The configuration files may be parameterized with either system properties (using <SystemProperty>
) or properties files (using <Property>
) passed via the command line. For example, this code in jetty.xml allows the port to be defined on the command line, falling back onto 8080 if the port was not specified:
<Set name="port"><SystemProperty name="jetty.port" default="8080"/></Set>
Then you modify the port while running Jetty by using this command:
java -Djetty.port=8888 -jar start.jar etc/jetty.xml
An example of defining both system properties and properties files from the command line:
java -Djetty.port=8888 -jar start.jar myjetty.properties etc/jetty.xml etc/other.xml