private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Jetty provides an XML-based configuration. It is grounded in Java's Reflection API. Classes in the java.lang.reflect represent Java methods and classes, such that you can instantiate objects and invoke their methods based on their names and argument types. Behind the scenes, Jetty's XML config parser translates the XML elements and attributes into Reflection calls.
jetty.xml, specify it as a configuration
file when running Jetty.
If you start Jetty without specifying a configuration file, Jetty
automatically locates and uses the default installation
jetty.xml file. Therefore
start.jar is equivalent to
java -jar start.jar
You are not limited to one configuration file; you can 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 the instance you want to configure.
Each server ID in a configuration file creates a new server instance
within the same JVM. If you use the same ID across multiple configuration
files, those configurations are all applied to the same server.
You can set parameters in configuration files either with system
<SystemProperty>) or properties
<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
the port is not specified:
Then you modify the port while running Jetty by using this command:
An example of defining both system properties and properties files from the command line: