Eclipse
/
jetty.project
mirror of https://github.com/jetty/jetty.project.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'jetty-9.4.x'

This commit is contained in:
Jesse McConnell 2016-06-09 14:18:52 -05:00
parent 5a91c4574a 147df2a031
commit c6172c9f2e
175 changed files with 1266 additions and 1164 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
jetty-distribution/pom.xml
View File

@ -217,6 +217,28 @@
</configuration> </configuration>
</execution> </execution>
<execution>
<id>unpack-test-webapp-config</id>
<phase>process-resources</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>org.eclipse.jetty</groupId>
<artifactId>test-jetty-webapp</artifactId>
<version>${project.version}</version>
<classifier>config</classifier>
<type>jar</type>
<overWrite>true</overWrite>
<outputDirectory>${assembly-directory}</outputDirectory>
</artifactItem>
</artifactItems>
<excludes>META-INF/**</excludes>
</configuration>
</execution>
<execution> <execution>
<id>unpack-test-jaas-config</id> <id>unpack-test-jaas-config</id>
<phase>process-resources</phase> <phase>process-resources</phase>
@ -524,21 +546,6 @@
<goal>java</goal> <goal>java</goal>
</goals> </goals>
</execution> </execution>
<execution>
<id>setup demo-base-ini</id>
<phase>process-classes</phase>
<configuration>
<mainClass>org.eclipse.jetty.start.Main</mainClass>
<arguments>
<argument>jetty.home=${assembly-directory}</argument>
<argument>jetty.base=${assembly-directory}/demo-base</argument>
<argument>--add-to-start=continuation,deploy,websocket,ext,resources,client,annotations,jndi,servlets</argument>
</arguments>
</configuration>
<goals>
<goal>java</goal>
</goals>
</execution>
<execution> <execution>
<id>setup demo-base-startd</id> <id>setup demo-base-startd</id>
<phase>process-classes</phase> <phase>process-classes</phase>
@ -547,7 +554,7 @@
<arguments> <arguments>
<argument>jetty.home=${assembly-directory}</argument> <argument>jetty.home=${assembly-directory}</argument>
<argument>jetty.base=${assembly-directory}/demo-base</argument> <argument>jetty.base=${assembly-directory}/demo-base</argument>
<argument>--add-to-startd=jsp,jstl,http,https</argument> <argument>--add-to-startd=continuation,deploy,websocket,ext,resources,client,annotations,jndi,servlets,jsp,jstl,http,https</argument>
</arguments> </arguments>
</configuration> </configuration>
<goals> <goals>

3
jetty-documentation/pom.xml
View File

@ -52,8 +52,8 @@
<doctype>book</doctype> <doctype>book</doctype>
<sourceDocumentName>index.adoc</sourceDocumentName> <sourceDocumentName>index.adoc</sourceDocumentName>
<attributes> <attributes>
<sub-order>attributes+</sub-order>
<imagesdir /> <imagesdir />
<version>${project.version}</version>
<linkcss>true</linkcss> <linkcss>true</linkcss>
<allow-uri-read>true</allow-uri-read> <allow-uri-read>true</allow-uri-read>
<toc>true</toc> <toc>true</toc>
@ -62,6 +62,7 @@
<JXURL>http://download.eclipse.org/jetty/stable-9/xref</JXURL> <JXURL>http://download.eclipse.org/jetty/stable-9/xref</JXURL>
<SRCDIR>${basedir}/..</SRCDIR> <SRCDIR>${basedir}/..</SRCDIR>
<GITBROWSEURL>https://github.com/eclipse/jetty.project/master</GITBROWSEURL> <GITBROWSEURL>https://github.com/eclipse/jetty.project/master</GITBROWSEURL>
<VERSION>${project.version}</VERSION>
</attributes> </attributes>
</configuration> </configuration>
</execution> </execution>

12
jetty-documentation/src/main/asciidoc/administration/alpn/alpn.adoc
View File

@ -42,7 +42,7 @@ This section provides the detail required for unusual deployments or developing
To enable ALPN support, start the JVM as follows: To enable ALPN support, start the JVM as follows:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
java -Xbootclasspath/p:<path_to_alpn_boot_jar> ... java -Xbootclasspath/p:<path_to_alpn_boot_jar> ...
---- ----
@ -75,7 +75,7 @@ Refer to `ALPN` Javadocs and to the examples below for further details about cli
[[alpn-client-example]] [[alpn-client-example]]
==== Client Example ==== Client Example
[source,java] [source, java, subs="{sub-order}"]
---- ----
SSLContext sslContext = ...; SSLContext sslContext = ...;
final SSLSocket sslSocket = (SSLSocket)context.getSocketFactory().createSocket("localhost", server.getLocalPort()); final SSLSocket sslSocket = (SSLSocket)context.getSocketFactory().createSocket("localhost", server.getLocalPort());
@ -121,7 +121,7 @@ The ALPN implementation calls `ALPN.ClientProvider` methods `supports()`, `proto
The example for SSLEngine is identical, and you just need to replace the SSLSocket instance with an SSLEngine instance. The example for SSLEngine is identical, and you just need to replace the SSLSocket instance with an SSLEngine instance.
[source,java] [source, java, subs="{sub-order}"]
---- ----
final SSLSocket sslSocket = ...; final SSLSocket sslSocket = ...;
ALPN.put(sslSocket, new ALPN.ServerProvider() ALPN.put(sslSocket, new ALPN.ServerProvider()
@ -159,7 +159,7 @@ Failing to do so will cause a memory leak.
You can write and run unit tests that use the ALPN implementation. You can write and run unit tests that use the ALPN implementation.
The solution that we use with Maven is to specify an additional command line argument to the Surefire plugin: The solution that we use with Maven is to specify an additional command line argument to the Surefire plugin:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project> <project>
@ -257,7 +257,7 @@ This section is for Jetty developers that need to update the ALPN implementation
Clone the OpenJDK repository with the following command: Clone the OpenJDK repository with the following command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ hg clone http://hg.openjdk.java.net/jdk7u/jdk7u jdk7u # OpenJDK 7 $ hg clone http://hg.openjdk.java.net/jdk7u/jdk7u jdk7u # OpenJDK 7
$ hg clone http://hg.openjdk.java.net/jdk8u/jdk8u jdk8u # OpenJDK 8 $ hg clone http://hg.openjdk.java.net/jdk8u/jdk8u jdk8u # OpenJDK 8
@ -268,7 +268,7 @@ $ ./get_source.sh
To update the source to a specific tag, use the following command: To update the source to a specific tag, use the following command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ ./make/scripts/hgforest.sh update <tag-name> $ ./make/scripts/hgforest.sh update <tag-name>

2
jetty-documentation/src/main/asciidoc/administration/annotations/quick-annotations-setup.adoc
View File

@ -37,7 +37,7 @@ Here is an example application that sets up the standard test-spec.war webapp fr
It can be found in the jetty git repository in the examples/embedded project. It can be found in the jetty git repository in the examples/embedded project.
Note that the test-spec.war uses not only annotations, but also link:#jndi[JNDI], so this example also enables their processing (via the link:#jndi-configuration-classes[org.eclipse.jetty.plus.webapp.EnvConfiguration], link:#jndi-configuration-classes[org.eclipse.jetty.plus.webapp.PlusConfiguration] and their related jars). Note that the test-spec.war uses not only annotations, but also link:#jndi[JNDI], so this example also enables their processing (via the link:#jndi-configuration-classes[org.eclipse.jetty.plus.webapp.EnvConfiguration], link:#jndi-configuration-classes[org.eclipse.jetty.plus.webapp.PlusConfiguration] and their related jars).
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ServerWithAnnotations.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ServerWithAnnotations.java[]
---- ----

4
jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations-embedded.adoc
View File

@ -35,7 +35,7 @@ This example also uses the @Resource annotation which involves JNDI, so we would
Here is the embedding code: Here is the embedding code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import org.eclipse.jetty.security.HashLoginService; import org.eclipse.jetty.security.HashLoginService;
import org.eclipse.jetty.server.Server; import org.eclipse.jetty.server.Server;
@ -97,7 +97,7 @@ On lines 30, 33 and 37 we set up some JNDI resources that we will be able to ref
With the setup above, we can create a servlet that uses annotations and Jetty will honour the annotations when the webapp is deployed: With the setup above, we can create a servlet that uses annotations and Jetty will honour the annotations when the webapp is deployed:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import javax.annotation.security.DeclareRoles; import javax.annotation.security.DeclareRoles;
import javax.annotation.security.RunAs; import javax.annotation.security.RunAs;

4
jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations.adoc
View File

@ -123,7 +123,7 @@ If you need ServletContainerInitializers called in a specific order that is diff
You may optionally use the wildcard character "*" *once* in the list. You may optionally use the wildcard character "*" *once* in the list.
It will match all ServletContainerInitializers not explicitly named in the list. Here's an example, setting the context attribute in code (although you can also do the link:#intro-jetty-configuration-webapps[same in xml]): It will match all ServletContainerInitializers not explicitly named in the list. Here's an example, setting the context attribute in code (although you can also do the link:#intro-jetty-configuration-webapps[same in xml]):
[source,java] [source, java, subs="{sub-order}"]
---- ----
WebAppContext context = new WebAppContext(); WebAppContext context = new WebAppContext();
context.setAttribute("org.eclipse.jetty.containerInitializerOrder", context.setAttribute("org.eclipse.jetty.containerInitializerOrder",
@ -142,7 +142,7 @@ In this case, you can define the `org.eclipse.jetty.containerInitializerExclusio
This is a regular expression that defines http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html[patterns] of classnames that you want to exclude. This is a regular expression that defines http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html[patterns] of classnames that you want to exclude.
Here's an example, setting the context attribute in code, although you may do exactly the link:#intro-jetty-configuration-webapps[same in xml]: Here's an example, setting the context attribute in code, although you may do exactly the link:#intro-jetty-configuration-webapps[same in xml]:
[source,java] [source, java, subs="{sub-order}"]
---- ----
WebAppContext context = new WebAppContext(); WebAppContext context = new WebAppContext();
context.setAttribute("org.eclipse.jetty.containerInitializerExclusionPattern", context.setAttribute("org.eclipse.jetty.containerInitializerExclusionPattern",

2
jetty-documentation/src/main/asciidoc/administration/extras/cross-origin-filter.adoc
View File

@ -77,7 +77,7 @@ exposedHeaders::
A typical configuration could be: A typical configuration could be:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<web-app> <web-app>

2
jetty-documentation/src/main/asciidoc/administration/extras/debug-handler.adoc
View File

@ -38,7 +38,7 @@ For example in start.ini.
==== Embedded usage ==== Embedded usage
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(8080); Server server = new Server(8080);
RolloverFileOutputStream outputStream = new RolloverFileOutputStream("MeinLogPfad/yyyy_mm_dd.request.log", true,10); RolloverFileOutputStream outputStream = new RolloverFileOutputStream("MeinLogPfad/yyyy_mm_dd.request.log", true,10);

2
jetty-documentation/src/main/asciidoc/administration/extras/default-handler.adoc
View File

@ -38,7 +38,7 @@ _____
The DefaultHandler will also handle serving out the flav.ico file should a request make it through all of the other handlers without being resolved. The DefaultHandler will also handle serving out the flav.ico file should a request make it through all of the other handlers without being resolved.
_____ _____
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(8080); Server server = new Server(8080);

2
jetty-documentation/src/main/asciidoc/administration/extras/dos-filter.adoc
View File

@ -54,7 +54,7 @@ Place the configuration in a webapp's web.xml or jetty-web.xml.
The default configuration allows 25 requests per connection at a time, servicing more important requests first, and queuing up the rest. The default configuration allows 25 requests per connection at a time, servicing more important requests first, and queuing up the rest.
This example allow 30 requests at a time: This example allow 30 requests at a time:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<filter> <filter>

2
jetty-documentation/src/main/asciidoc/administration/extras/moved-context-handler.adoc
View File

@ -46,7 +46,7 @@ You create a new context xml file in $JETTY_HOME/contexts and configure the Move
Here's an example. Here's an example.
This is a permanent redirection, which also preserves pathinfo and query strings on the redirect: This is a permanent redirection, which also preserves pathinfo and query strings on the redirect:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>

6
jetty-documentation/src/main/asciidoc/administration/extras/qos-filter.adoc
View File

@ -83,7 +83,7 @@ Place the configuration in a webapp's web.xml or jetty-web.xml.
The default configuration processes ten requests at a time, servicing more important requests first, and queuing up the rest. The default configuration processes ten requests at a time, servicing more important requests first, and queuing up the rest.
This example processes fifty requests at a time: This example processes fifty requests at a time:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<filter> <filter>
@ -129,7 +129,7 @@ managedAttr::
You can use the `<filter-mapping>` syntax to map the QoSFilter to a servlet, either by using the servlet name, or by using a URL pattern. You can use the `<filter-mapping>` syntax to map the QoSFilter to a servlet, either by using the servlet name, or by using a URL pattern.
In this example, a URL pattern applies the QoSFilter to every request within the web application context: In this example, a URL pattern applies the QoSFilter to every request within the web application context:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<filter-mapping> <filter-mapping>
@ -153,7 +153,7 @@ To customize the priority, subclass QoSFilter and then override the getPriority(
You can then use this subclass as your QoS filter. You can then use this subclass as your QoS filter.
Here's a trivial example: Here's a trivial example:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public class ParsePriorityQoSFilter extends QoSFilter public class ParsePriorityQoSFilter extends QoSFilter

2
jetty-documentation/src/main/asciidoc/administration/extras/resource-handler.adoc
View File

@ -50,7 +50,7 @@ The default css is called jetty-dir.css and is located in the jetty-util package
The following is an example of a split fileserver, able to serve static content from multiple directory locations. The following is an example of a split fileserver, able to serve static content from multiple directory locations.
Since this handler does not return 404's on content you are able to iteratively try multiple resource handlers to resolve content. Since this handler does not return 404's on content you are able to iteratively try multiple resource handlers to resolve content.
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SplitFileServer.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SplitFileServer.java[]
---- ----

8
jetty-documentation/src/main/asciidoc/administration/extras/rewrite-handler.adoc
View File

@ -29,7 +29,7 @@ The RewriteHandler matches a request against a set of rules, and modifies the re
The standard Jetty distribution bundle contains the `jetty-rewrite` link:#startup-modules[module], so all you need to do is to enable it using one of the link:#start-jar[module commands], eg: The standard Jetty distribution bundle contains the `jetty-rewrite` link:#startup-modules[module], so all you need to do is to enable it using one of the link:#start-jar[module commands], eg:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ java -jar start.jar --add-to-startd=rewrite $ java -jar start.jar --add-to-startd=rewrite
@ -45,7 +45,7 @@ _____
The rewrite module enables the following jetty xml config file on the execution path: The rewrite module enables the following jetty xml config file on the execution path:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-rewrite/src/main/config/etc/jetty-rewrite.xml[] include::{SRCDIR}/jetty-rewrite/src/main/config/etc/jetty-rewrite.xml[]
---- ----
@ -54,7 +54,7 @@ As the commented out code shows, you configure the RewriteHandler by adding vari
There is an example of link:#rewrite-rules[rules] configuration in the standard distribution in the `demo-base/etc/demo-rewrite-rules.xml` file: There is an example of link:#rewrite-rules[rules] configuration in the standard distribution in the `demo-base/etc/demo-rewrite-rules.xml` file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/tests/test-webapps/test-jetty-webapp/src/main/config/demo-base/etc/demo-rewrite-rules.xml[] include::{SRCDIR}/tests/test-webapps/test-jetty-webapp/src/main/config/demo-base/etc/demo-rewrite-rules.xml[]
---- ----
@ -63,7 +63,7 @@ include::{SRCDIR}/tests/test-webapps/test-jetty-webapp/src/main/config/demo-base
This is an example for embedded Jetty, which does something similar to the configuration file example above: This is an example for embedded Jetty, which does something similar to the configuration file example above:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(); Server server = new Server();

4
jetty-documentation/src/main/asciidoc/administration/extras/shutdown-handler.adoc
View File

@ -34,7 +34,7 @@ If _exitJvm is set to true a hard System.exit() call is being made.
This is an example of how you can setup this handler directly with the Server, it can be added as a part of handler chain or collection as well. This is an example of how you can setup this handler directly with the Server, it can be added as a part of handler chain or collection as well.
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(8080); Server server = new Server(8080);
@ -49,7 +49,7 @@ This is an example of how you can setup this handler directly with the Server, i
And this is an example that you can use to call the shutdown handler from within java. And this is an example that you can use to call the shutdown handler from within java.
[source,java] [source, java, subs="{sub-order}"]
---- ----
public static void attemptShutdown(int port, String shutdownCookie) { public static void attemptShutdown(int port, String shutdownCookie) {

6
jetty-documentation/src/main/asciidoc/administration/extras/statistics-handler.adoc
View File

@ -55,7 +55,7 @@ To learn how to turn on connector statistics please see Jetty Statistics tutoria
The following example shows how to turn on connector statistics in jetty xml. The following example shows how to turn on connector statistics in jetty xml.
This example comes from within `jetty-http.xml`. This example comes from within `jetty-http.xml`.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Call name="addConnector"> <Call name="addConnector">
@ -95,7 +95,7 @@ Typically this can be done as the top level handler, but you may choose to confi
Please note that `jetty-stats.xml` has to appear in the command line after the main Jetty configuration file as shown below. Please note that `jetty-stats.xml` has to appear in the command line after the main Jetty configuration file as shown below.
It should be able to be uncommented in the start.ini file. It should be able to be uncommented in the start.ini file.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ java -jar start.jar OPTIONS=default etc/jetty.xml etc/jetty-stats.xml $ java -jar start.jar OPTIONS=default etc/jetty.xml etc/jetty-stats.xml
@ -104,7 +104,7 @@ $ java -jar start.jar OPTIONS=default etc/jetty.xml etc/jetty-stats.xml
Alternately, if you are making multiple changes to the Jetty configuration, you could include statistics handler configuration into your own jetty xml configuration. Alternately, if you are making multiple changes to the Jetty configuration, you could include statistics handler configuration into your own jetty xml configuration.
The following fragment shows how to configure a top level statistics handler: The following fragment shows how to configure a top level statistics handler:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Get id="oldhandler" name="handler" /> <Get id="oldhandler" name="handler" />

10
jetty-documentation/src/main/asciidoc/administration/fastcgi/configuring-fastcgi.adoc
View File

@ -29,7 +29,7 @@ Refer to xref:jetty-downloading[] for more information about how to install Jett
The fourth step is to create a Jetty base directory (see xref:startup-base-and-home[]), called in the following `$JETTY_BASE`, where you setup the configuration needed to support FastCGI in Jetty, and configure the `fcgi`, `http` and `deploy` modules, so that Jetty will be able to accept HTTP requests from browsers, convert them in FastCGI, and proxy them to `php-fpm`: The fourth step is to create a Jetty base directory (see xref:startup-base-and-home[]), called in the following `$JETTY_BASE`, where you setup the configuration needed to support FastCGI in Jetty, and configure the `fcgi`, `http` and `deploy` modules, so that Jetty will be able to accept HTTP requests from browsers, convert them in FastCGI, and proxy them to `php-fpm`:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ mkdir -p /usr/jetty/wordpress $ mkdir -p /usr/jetty/wordpress
$ cd /usr/jetty/wordpress $ cd /usr/jetty/wordpress
@ -44,7 +44,7 @@ Typically this is done by deploying a `*.war` file in the `$JETTY_BASE/webapps`
Therefore you just need to deploy a Jetty XML file that configures the web application directly. Therefore you just need to deploy a Jetty XML file that configures the web application directly.
Copy and paste the following content as `$JETTY_BASE/webapps/jetty-wordpress.xml` Copy and paste the following content as `$JETTY_BASE/webapps/jetty-wordpress.xml`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://www.eclipse.org/jetty/configure_9_3.dtd"> <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://www.eclipse.org/jetty/configure_9_3.dtd">
@ -135,7 +135,7 @@ Refer to the link:{JDURL}/org/eclipse/jetty/fcgi/server/proxy/FastCGIProxyServle
The last step is to start Jetty (see xref:startup[]) and hit `http://localhost:8080` with your browser and enjoy WordPress: The last step is to start Jetty (see xref:startup[]) and hit `http://localhost:8080` with your browser and enjoy WordPress:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ cd $JETTY_BASE $ cd $JETTY_BASE
$ java -jar /opt/jetty/start.jar $ java -jar /opt/jetty/start.jar
@ -149,7 +149,7 @@ In order to configure Jetty to listen for HTTP/2 requests from clients that are
Enabling the `http2` is really simple; in additions to the modules you have enabled above, add the `http2` module: Enabling the `http2` is really simple; in additions to the modules you have enabled above, add the `http2` module:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ cd $JETTY_BASE $ cd $JETTY_BASE
$ java -jar $JETTY_HOME/start.jar --add-to-start=http2 $ java -jar $JETTY_HOME/start.jar --add-to-start=http2
@ -170,7 +170,7 @@ These will setup a clear text connector on port 8080 for HTTP/1.1 and a TLS conn
At this point, you can start Jetty (see xref:startup[]), hit `http://localhost:8080` with your browser and enjoy WordPress via HTTP/2 using a HTTP/2 enabled browser: At this point, you can start Jetty (see xref:startup[]), hit `http://localhost:8080` with your browser and enjoy WordPress via HTTP/2 using a HTTP/2 enabled browser:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ cd $JETTY_BASE $ cd $JETTY_BASE
$ java -jar $JETTY_HOME/start.jar $ java -jar $JETTY_HOME/start.jar

2
jetty-documentation/src/main/asciidoc/administration/http2/configuring-push.adoc
View File

@ -22,7 +22,7 @@ This will reduce the amount of round-trips necessary to retrieve all the resourc
HTTP/2 Push can be automated in your application by simply configuring a link:{JDURL}/org/eclipse/jetty/servlets/PushCacheFilter.html[`PushCacheFilter`] in your `web.xml`, in this way: HTTP/2 Push can be automated in your application by simply configuring a link:{JDURL}/org/eclipse/jetty/servlets/PushCacheFilter.html[`PushCacheFilter`] in your `web.xml`, in this way:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>

2
jetty-documentation/src/main/asciidoc/administration/http2/enabling-http2.adoc
View File

@ -19,7 +19,7 @@
This section is written assuming that a jetty base directory is being used and a demo jetty base that support HTTP/1, HTTPS/1 and deployment from a webapps directory can be created with the commands: This section is written assuming that a jetty base directory is being used and a demo jetty base that support HTTP/1, HTTPS/1 and deployment from a webapps directory can be created with the commands:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ JETTY_BASE=http2-demo $ JETTY_BASE=http2-demo
$ mkdir $JETTY_BASE $ mkdir $JETTY_BASE

4
jetty-documentation/src/main/asciidoc/administration/jmx/jetty-jconsole.adoc
View File

@ -29,7 +29,7 @@ To monitor Jetty's server status with JConsole, make sure JConsole is running, a
The simplest way to enable support is to add the jmx support module to your $\{jetty.base}. The simplest way to enable support is to add the jmx support module to your $\{jetty.base}.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ java /opt/jetty-dist/start.jar --add-to-start=jmx [mybase]$ java /opt/jetty-dist/start.jar --add-to-start=jmx
INFO: jmx-remote initialised in ${jetty.base}/start.ini (appended) INFO: jmx-remote initialised in ${jetty.base}/start.ini (appended)
@ -61,7 +61,7 @@ The way to do this is to set your MAVEN_OPTS environment variable (if you're not
Here is an example that sets the system property on the fly in a BASH shell, before starting Jetty via the plugin: Here is an example that sets the system property on the fly in a BASH shell, before starting Jetty via the plugin:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ export MAVEN_OPTS=-Dcom.sun.management.jmxremote $ export MAVEN_OPTS=-Dcom.sun.management.jmxremote

2
jetty-documentation/src/main/asciidoc/administration/jmx/jetty-jmx-annotations.adoc
View File

@ -100,7 +100,7 @@ description::
The following is an example of each of the annotations mentioned above in practice. The following is an example of each of the annotations mentioned above in practice.
[source,java] [source, java, subs="{sub-order}"]
---- ----
package com.acme; package com.acme;

13
jetty-documentation/src/main/asciidoc/administration/jmx/using-jmx.adoc
View File

@ -33,7 +33,7 @@ This implementation allows you to wrap an arbitrary POJO in an MBean and annotat
See xref:jetty-jmx-annotations[]. See xref:jetty-jmx-annotations[].
TheMBeanContainer implementation of the Container.Listener interface coordinates creation of MBeans. TheMBeanContainer implementation of the Container.Listener interface coordinates creation of MBeans.
The Jetty Server and it's components use a link:{JDURL}/org/eclipse/jetty/util/component/Container.html[Container] to maintain a containment tree of components and to support notification of changes to that tree. The Jetty Server and it's components use a link:{JDURL}/org/eclipse/jetty/util/component/Container.html[Container] to maintain a containment tree of components and to support notification of changes to that tree.
The MBeanContainer class listens for Container events and creates and destroys MBeans as required to wrap all Jetty components. The MBeanContainer class listens for Container events and creates and destroys MBeans as required to wrap all Jetty components.
You can access the MBeans that Jetty publishes both through built-in Java VM connector via JConsole, or by registering a remote JMX connector and using a remote JMX agent to monitor Jetty. You can access the MBeans that Jetty publishes both through built-in Java VM connector via JConsole, or by registering a remote JMX connector and using a remote JMX agent to monitor Jetty.
@ -76,7 +76,7 @@ If you are having difficulties validate that the section in the jetty.home/start
When running Jetty embedded into an application, create and configure an MBeanContainer instance as follows: When running Jetty embedded into an application, create and configure an MBeanContainer instance as follows:
[source,java] [source, java]
---- ----
Server server = new Server(); Server server = new Server();
@ -100,12 +100,12 @@ Because logging is initialized prior to the MBeanContainer (even before the Serv
If you are using the link:#jetty-maven-plugin[jetty maven plugin] you should copy the `etc/jetty-jmx.xml` file into your webapp project somewhere, such as `src/etc,` then add a `<jettyconfig>` element to the plugin `<configuration>`: If you are using the link:#jetty-maven-plugin[jetty maven plugin] you should copy the `etc/jetty-jmx.xml` file into your webapp project somewhere, such as `src/etc,` then add a `<jettyconfig>` element to the plugin `<configuration>`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<plugin> <plugin>
<groupid>org.eclipse.jetty</groupid> <groupid>org.eclipse.jetty</groupid>
<artifactid>jetty-maven-plugin</artifactid> <artifactid>jetty-maven-plugin</artifactid>
<version>@project.version@</version> <version>{VERSION}</version>
<configuration> <configuration>
<scanintervalseconds>10</scanintervalseconds> <scanintervalseconds>10</scanintervalseconds>
<jettyXml>src/etc/jetty-jmx.xml</jettyXml> <jettyXml>src/etc/jetty-jmx.xml</jettyXml>
@ -114,6 +114,7 @@ If you are using the link:#jetty-maven-plugin[jetty maven plugin] you should cop
---- ----
[[enabling-jmxconnectorserver-for-remote-access]] [[enabling-jmxconnectorserver-for-remote-access]]
==== Enabling JMXConnectorServer for Remote Access ==== Enabling JMXConnectorServer for Remote Access
@ -124,7 +125,7 @@ Unfortunately, this solution does not play well with firewalls and it is not fle
* Use Jetty's `ConnectorServer` class. * Use Jetty's `ConnectorServer` class.
To enable use of this class, uncomment the correspondent portion in `etc/jetty-jmx.xml,` like this: To enable use of this class, uncomment the correspondent portion in `etc/jetty-jmx.xml,` like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="ConnectorServer" class="org.eclipse.jetty.jmx.ConnectorServer"> <New id="ConnectorServer" class="org.eclipse.jetty.jmx.ConnectorServer">
<Arg> <Arg>
@ -151,7 +152,7 @@ For a complete guide to controlling authentication and authorization in JMX, see
To restrict access to the JMXConnectorServer, you can use this configuration, where the `jmx.password` and `jmx.access` files have the format specified in the blog entry above: To restrict access to the JMXConnectorServer, you can use this configuration, where the `jmx.password` and `jmx.access` files have the format specified in the blog entry above:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="ConnectorServer" class="org.eclipse.jetty.jmx.ConnectorServer"> <New id="ConnectorServer" class="org.eclipse.jetty.jmx.ConnectorServer">

28
jetty-documentation/src/main/asciidoc/administration/jndi/jndi-configuration.adoc
View File

@ -25,7 +25,7 @@ runtime that you either cannot or cannot conveniently code into a
`web.xml env-entry`. In such cases, you can use `org.eclipse.jetty.plus.jndi.EnvEntry`, and even override an entry of `web.xml env-entry`. In such cases, you can use `org.eclipse.jetty.plus.jndi.EnvEntry`, and even override an entry of
the same name in ` web.xml`. the same name in ` web.xml`.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.plus.jndi.EnvEntry"> <New class="org.eclipse.jetty.plus.jndi.EnvEntry">
<Arg></Arg> <Arg></Arg>
@ -66,7 +66,7 @@ application is __not portable__.
To use the `env-entry` configured above, use code in your To use the `env-entry` configured above, use code in your
`servlet/filter/etc.`, such as: `servlet/filter/etc.`, such as:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import javax.naming.InitialContext; import javax.naming.InitialContext;
@ -121,7 +121,7 @@ relational database, but you can use any implementation of a
`javax.sql.DataSource`. This example configures it as scoped to a web `javax.sql.DataSource`. This example configures it as scoped to a web
app with the id of __wac__: app with the id of __wac__:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">
<New id="myds" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="myds" class="org.eclipse.jetty.plus.jndi.Resource">
@ -147,7 +147,7 @@ from application lookups as `
Here's an example `web.xml` declaration for the datasource above: Here's an example `web.xml` declaration for the datasource above:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<resource-ref> <resource-ref>
<res-ref-name>jdbc/myds</res-ref-name> <res-ref-name>jdbc/myds</res-ref-name>
@ -158,7 +158,7 @@ Here's an example `web.xml` declaration for the datasource above:
To look up your DataSource in your `servlet/filter/etc.`: To look up your DataSource in your `servlet/filter/etc.`:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import javax.naming.InitialContext; import javax.naming.InitialContext;
import javax.sql.DataSource; import javax.sql.DataSource;
@ -192,7 +192,7 @@ factories. You just need to ensure the implementation Jars are available
on Jetty's classpath. Here is an example of binding an on Jetty's classpath. Here is an example of binding an
http://activemq.apache.org[ActiveMQ] in-JVM connection factory: http://activemq.apache.org[ActiveMQ] in-JVM connection factory:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">
<New id="cf" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="cf" class="org.eclipse.jetty.plus.jndi.Resource">
@ -209,7 +209,7 @@ http://activemq.apache.org[ActiveMQ] in-JVM connection factory:
The entry in `web.xml` would be: The entry in `web.xml` would be:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<resource-ref> <resource-ref>
<res-ref-name>jms/connectionFactory</res-ref-name> <res-ref-name>jms/connectionFactory</res-ref-name>
@ -226,7 +226,7 @@ TODO: put in an example of a QUEUE from progress demo
Jetty also provides infrastructure for access to `javax.mail.Sessions` Jetty also provides infrastructure for access to `javax.mail.Sessions`
from within an application: from within an application:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">
<New id="mail" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="mail" class="org.eclipse.jetty.plus.jndi.Resource">
@ -276,7 +276,7 @@ link:{JDURL}/org/eclipse/jetty/plus/jndi/Transaction.html[JNDI
Transaction] object in a Jetty config file. The following example Transaction] object in a Jetty config file. The following example
configures the http://www.atomikos.com/[Atomikos] transaction manager: configures the http://www.atomikos.com/[Atomikos] transaction manager:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="tx" class="org.eclipse.jetty.plus.jndi.Transaction"> <New id="tx" class="org.eclipse.jetty.plus.jndi.Transaction">
<Arg> <Arg>
@ -293,7 +293,7 @@ you use for it in `web.xml`. For example:
In a context xml file: In a context xml file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">
<New id="myds" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="myds" class="org.eclipse.jetty.plus.jndi.Resource">
@ -311,7 +311,7 @@ In a context xml file:
In `web.xml`: In `web.xml`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<resource-ref> <resource-ref>
<res-ref-name>jdbc/mydatasource</res-ref-name> <res-ref-name>jdbc/mydatasource</res-ref-name>
@ -333,7 +333,7 @@ to the `jdbc/mydatasource` resource as `
In a context xml file declare `jdbc/mydatasource`: In a context xml file declare `jdbc/mydatasource`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">
<New id="myds" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="myds" class="org.eclipse.jetty.plus.jndi.Resource">
@ -353,7 +353,7 @@ Then in a `WEB-INF/jetty-env.xml` file, link the name
`jdbc/mydatasource` to the name you want to reference it as in `jdbc/mydatasource` to the name you want to reference it as in
`web.xml`, which in this case is `jdbc/mydatasource1`: `web.xml`, which in this case is `jdbc/mydatasource1`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="map1" class="org.eclipse.jetty.plus.jndi.Link"> <New id="map1" class="org.eclipse.jetty.plus.jndi.Link">
<Arg><Ref refid='wac'/></Arg> <Arg><Ref refid='wac'/></Arg>
@ -364,7 +364,7 @@ Then in a `WEB-INF/jetty-env.xml` file, link the name
Now you can refer to `jdbc/mydatasource1` in the `web.xml` like this: Now you can refer to `jdbc/mydatasource1` in the `web.xml` like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<resource-ref> <resource-ref>
<res-ref-name>jdbc/mydatasource1</res-ref-name> <res-ref-name>jdbc/mydatasource1</res-ref-name>

28
jetty-documentation/src/main/asciidoc/administration/jndi/jndi-datasources.adoc
View File

@ -27,7 +27,7 @@ ____
All of these examples correspond to a `resource-ref` in `web.xml`. All of these examples correspond to a `resource-ref` in `web.xml`.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<resource-ref> <resource-ref>
@ -80,7 +80,7 @@ http://search.maven.org/remotecontent?filepath=com/zaxxer/HikariCP/1.4.0/HikariC
Download]. All configuration options for HikariCP are described here: Download]. All configuration options for HikariCP are described here:
https://github.com/brettwooldridge/HikariCP[HikariCP documentation]. https://github.com/brettwooldridge/HikariCP[HikariCP documentation].
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -117,7 +117,7 @@ Download]. All configuration options for BoneCP are described here:
http://jolbox.com/bonecp/downloads/site/apidocs/com/jolbox/bonecp/BoneCPDataSource.html[BoneCP http://jolbox.com/bonecp/downloads/site/apidocs/com/jolbox/bonecp/BoneCPDataSource.html[BoneCP
API]. API].
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -147,7 +147,7 @@ Connection pooling, available at
http://central.maven.org/maven2/c3p0/c3p0/0.9.1.2/c3p0-0.9.1.2.jar[c3p0 http://central.maven.org/maven2/c3p0/c3p0/0.9.1.2/c3p0-0.9.1.2.jar[c3p0
Jar]. Jar].
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -173,7 +173,7 @@ Connection pooling, available at
http://central.maven.org/maven2/commons-dbcp/commons-dbcp/1.2/commons-dbcp-1.2.jar[dbcp http://central.maven.org/maven2/commons-dbcp/commons-dbcp/1.2/commons-dbcp-1.2.jar[dbcp
Jar]. Jar].
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -198,7 +198,7 @@ Jar].
Connection pooling + XA transactions. Connection pooling + XA transactions.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -237,7 +237,7 @@ Connection pooling + XA transactions.
Implements `javax.sql.DataSource, Implements `javax.sql.DataSource,
javax.sql.ConnectionPoolDataSource.` javax.sql.ConnectionPoolDataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -260,7 +260,7 @@ Implements `javax.sql.DataSource,
Implements `javax.sql.ConnectionPoolDataSource` Implements `javax.sql.ConnectionPoolDataSource`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -286,7 +286,7 @@ Implements `javax.sql.ConnectionPoolDataSource`
Implements `javax.sql.ConnectionPoolDataSource` Implements `javax.sql.ConnectionPoolDataSource`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
@ -327,7 +327,7 @@ The following is a list of the non-pooled datasource examples:
Implements `javax.sql.DataSource, Implements `javax.sql.DataSource,
javax.sql.ConnectionPoolDataSource.` javax.sql.ConnectionPoolDataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg></Arg>
@ -350,7 +350,7 @@ Implements `javax.sql.DataSource,
Implements `javax.sql.DataSource, Implements `javax.sql.DataSource,
javax.sql.ConnectionPoolDataSource.` javax.sql.ConnectionPoolDataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg></Arg>
@ -385,7 +385,7 @@ Database JDBC documentation].
Implements `javax.sql.DataSource.` Implements `javax.sql.DataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg></Arg>
@ -407,7 +407,7 @@ Implements `javax.sql.DataSource.`
Implements `javax.sql.DataSource.` Implements `javax.sql.DataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg></Arg>
@ -429,7 +429,7 @@ Implements `javax.sql.DataSource.`
Implements `javax.sql.DataSource.` Implements `javax.sql.DataSource.`
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg> <Arg></Arg>

2
jetty-documentation/src/main/asciidoc/administration/jndi/jndi-embedded.adoc
View File

@ -52,7 +52,7 @@ webapp that references these JNDI entries in code. We'll use some mocked
up classes for the transaction manager and the DataSource in this up classes for the transaction manager and the DataSource in this
example for simplicity: example for simplicity:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import java.util.Properties; import java.util.Properties;
import org.eclipse.jetty.server.Server; import org.eclipse.jetty.server.Server;

10
jetty-documentation/src/main/asciidoc/administration/jndi/using-jndi.adoc
View File

@ -24,7 +24,7 @@ access from within the `java:comp/env` naming environment of the webapp
during execution. Specifically, you can configure support for the during execution. Specifically, you can configure support for the
following `web.xml` elements: following `web.xml` elements:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<env-entry/> <env-entry/>
@ -65,7 +65,7 @@ these bindings by using declarations of the following types:
Declarations of each of these types follow the same general pattern: Declarations of each of these types follow the same general pattern:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.plus.jndi.xxxx"> <New class="org.eclipse.jetty.plus.jndi.xxxx">
@ -116,7 +116,7 @@ JVM scope::
application code. You represent this scope by a `null` first parameter application code. You represent this scope by a `null` first parameter
to the resource declaration. For example: to the resource declaration. For example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="cf" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="cf" class="org.eclipse.jetty.plus.jndi.Resource">
@ -137,7 +137,7 @@ Server scope::
the Server instance as the first parameter to the resource the Server instance as the first parameter to the resource
declaration. For example: declaration. For example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.Server"> <Configure id="Server" class="org.eclipse.jetty.Server">
@ -160,7 +160,7 @@ Webapp scope::
referencing the WebAppContext instance as the first parameter to the referencing the WebAppContext instance as the first parameter to the
resource declaration. For example: resource declaration. For example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext">

6
jetty-documentation/src/main/asciidoc/administration/logging/configuring-jetty-request-logs.adoc
View File

@ -46,7 +46,7 @@ If neither of these options meets your needs, you can implement a custom request
To configure a single request log for the entire Jetty Server instance: To configure a single request log for the entire Jetty Server instance:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.server.Server"> <Configure id="Server" class="org.eclipse.jetty.server.Server">
<Set name="RequestLog"> <Set name="RequestLog">
@ -62,7 +62,7 @@ To configure a single request log for the entire Jetty Server instance:
The equivalent code is: The equivalent code is:
[source,java] [source, java, subs="{sub-order}"]
---- ----
NCSARequestLog requestLog = new NCSARequestLog("/var/logs/jetty/jetty-yyyy_mm_dd.request.log"); NCSARequestLog requestLog = new NCSARequestLog("/var/logs/jetty/jetty-yyyy_mm_dd.request.log");
requestLog.setAppend(true); requestLog.setAppend(true);
@ -83,7 +83,7 @@ To examine many more configuration options, see link:{JDURL}/org/eclipse/jetty/s
To configure a separate request log for a web application, add the following to the context XML file. To configure a separate request log for a web application, add the following to the context XML file.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
... ...

4
jetty-documentation/src/main/asciidoc/administration/logging/default-logging-with-stderrlog.adoc
View File

@ -85,7 +85,7 @@ There are a number of properties that can be defined in the configuration that w
+ +
* Example when set to false: * Example when set to false:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
2014-06-03 14:36:16.013:INFO:oejs.Server:main: jetty-9.2.0.v20140526 2014-06-03 14:36:16.013:INFO:oejs.Server:main: jetty-9.2.0.v20140526
2014-06-03 14:36:16.028:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/demo-base/webapps/] at interval 1 2014-06-03 14:36:16.028:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/demo-base/webapps/] at interval 1
@ -96,7 +96,7 @@ There are a number of properties that can be defined in the configuration that w
+ +
* Example when set to true: * Example when set to true:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
2014-06-03 14:38:19.019:INFO:org.eclipse.jetty.server.Server:main: jetty-9.2.0.v20140526 2014-06-03 14:38:19.019:INFO:org.eclipse.jetty.server.Server:main: jetty-9.2.0.v20140526
2014-06-03 14:38:19.032:INFO:org.eclipse.jetty.deploy.providers.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/demo-base/webapps/] at interval 1 2014-06-03 14:38:19.032:INFO:org.eclipse.jetty.deploy.providers.ScanningAppProvider:main: Deployment monitor [file:/opt/jetty/demo-base/webapps/] at interval 1

320
jetty-documentation/src/main/asciidoc/administration/logging/dump-tool.adoc
View File

@ -27,7 +27,7 @@ You can do this by a direct call if you are embedding Jetty, or in `jetty.xml`.
You can request that Jetty do a dump immediately after staring and just before stopping by calling the appropriate setters on the Server instance. You can request that Jetty do a dump immediately after staring and just before stopping by calling the appropriate setters on the Server instance.
This can be accomplished in `jetty.xml` with: This can be accomplished in `jetty.xml` with:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Set name="dumpAfterStart">true</Set> <Set name="dumpAfterStart">true</Set>
<Set name="dumpBeforeStop">true</Set> <Set name="dumpBeforeStop">true</Set>
@ -39,7 +39,7 @@ This can be accomplished in `jetty.xml` with:
You can get additional detail from the QueuedThreadPool if `setDetailedDump(true)` is called on the thread pool instance. You can get additional detail from the QueuedThreadPool if `setDetailedDump(true)` is called on the thread pool instance.
Do this in `jetty.xml` as follows: Do this in `jetty.xml` as follows:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.server.Server"> <Configure id="Server" class="org.eclipse.jetty.server.Server">
<!-- ==================================== --> <!-- ==================================== -->
@ -223,7 +223,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED | | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED
| | | | | | | +- logVerbosityLevel=DEBUG | | | | | | | +- logVerbosityLevel=DEBUG
| | | | | | | +- fork=false | | | | | | | +- fork=false
| | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-@project.version@/resources:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar:/home/user/jetty-distribution-@project.version@/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib | | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-{VERSION}/resources:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib
| | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/jsp | | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/jsp
| | | | | | | +- xpoweredBy=false | | | | | | | +- xpoweredBy=false
| | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp | | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp
@ -250,42 +250,42 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | +> WebAppClassLoader=Async REST Webservice Example@52934ea0 | | | +> WebAppClassLoader=Async REST Webservice Example@52934ea0
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/classes/ | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/classes/
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-client-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-client-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-ajax-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-ajax-{VERSION}.jar
| | | | +- startJarLoader@7194b34a | | | | +- startJarLoader@7194b34a
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/resources/ | | | | +- file:/home/user/jetty-distribution-{VERSION}/resources/
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar
| | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b | | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b
| | | | +- file:/home/user/jetty-distribution-@project.version@/start.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/start.jar
| | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b | | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b
| | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any- | | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-
| | | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-client-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-ajax-@project.version@.jar | | | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-client-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/jetty-util-ajax-{VERSION}.jar
| | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$ | | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$
| | | +> com.sun.jsp.taglibraryCache={} | | | +> com.sun.jsp.taglibraryCache={}
| | | +> com.sun.jsp.tagFileJarUrlsCache={} | | | +> com.sun.jsp.tagFileJarUrlsCache={}
@ -296,7 +296,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | | |
| | | +> No ClassLoader | | | +> No ClassLoader
| | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$ | | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$
| | += o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-@project.version@/webapps/ROOT/,AVAILABLE}{/ROOT} - STARTED | | += o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-{VERSION}/webapps/ROOT/,AVAILABLE}{/ROOT} - STARTED
| | | += org.eclipse.jetty.server.session.SessionHandler@5a770658 - STARTED | | | += org.eclipse.jetty.server.session.SessionHandler@5a770658 - STARTED
| | | | += org.eclipse.jetty.server.session.HashSessionManager@746a95ae - STARTED | | | | += org.eclipse.jetty.server.session.HashSessionManager@746a95ae - STARTED
| | | | += org.eclipse.jetty.security.ConstraintSecurityHandler@1890e38 - STARTED | | | | += org.eclipse.jetty.security.ConstraintSecurityHandler@1890e38 - STARTED
@ -318,7 +318,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED | | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED
| | | | | | | +- logVerbosityLevel=DEBUG | | | | | | | +- logVerbosityLevel=DEBUG
| | | | | | | +- fork=false | | | | | | | +- fork=false
| | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-@project.version@/resources:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar:/home/user/jetty-distribution-@project.version@/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib | | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-{VERSION}/resources:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib
| | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-ROOT-_-any-/jsp | | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-ROOT-_-any-/jsp
| | | | | | | +- xpoweredBy=false | | | | | | | +- xpoweredBy=false
| | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp | | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp
@ -340,39 +340,39 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | | |
| | | +> WebAppClassLoader=ROOT@7af33249 | | | +> WebAppClassLoader=ROOT@7af33249
| | | | +- startJarLoader@7194b34a | | | | +- startJarLoader@7194b34a
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/resources/ | | | | +- file:/home/user/jetty-distribution-{VERSION}/resources/
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar
| | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b | | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b
| | | | +- file:/home/user/jetty-distribution-@project.version@/start.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/start.jar
| | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b | | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b
| | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-ROOT-_-any- | | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-ROOT-_-any-
| | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$ | | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$
| | | +> com.sun.jsp.taglibraryCache={} | | | +> com.sun.jsp.taglibraryCache={}
| | | +> com.sun.jsp.tagFileJarUrlsCache={} | | | +> com.sun.jsp.tagFileJarUrlsCache={}
| | += o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-@project.version@/javadoc,AVAILABLE} - STARTED | | += o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-{VERSION}/javadoc,AVAILABLE} - STARTED
| | | += org.eclipse.jetty.server.handler.ResourceHandler@8f9c8a7 - STARTED | | | += org.eclipse.jetty.server.handler.ResourceHandler@8f9c8a7 - STARTED
| | | | +~ org.eclipse.jetty.jmx.MBeanContainer@644a5ddd | | | | +~ org.eclipse.jetty.jmx.MBeanContainer@644a5ddd
| | | +~ org.eclipse.jetty.jmx.MBeanContainer@644a5ddd | | | +~ org.eclipse.jetty.jmx.MBeanContainer@644a5ddd
@ -401,7 +401,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED | | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED
| | | | | | | +- logVerbosityLevel=DEBUG | | | | | | | +- logVerbosityLevel=DEBUG
| | | | | | | +- fork=false | | | | | | | +- fork=false
| | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-@project.version@/resources:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar:/home/user/jetty-distribution-@project.version@/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib | | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-{VERSION}/resources:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib
| | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/jsp | | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/jsp
| | | | | | | +- xpoweredBy=false | | | | | | | +- xpoweredBy=false
| | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp | | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp
@ -484,46 +484,46 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | | | |
| | | +> WebAppClassLoader=Test WebApp@3e2f3adb | | | +> WebAppClassLoader=Test WebApp@3e2f3adb
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/classes/ | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/classes/
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-continuation-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-continuation-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-servlets-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-servlets-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-api-9.0.2.v20130417.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-api-9.0.2.v20130417.jar
| | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-servlet-9.0.2.v20130417.jar | | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-servlet-9.0.2.v20130417.jar
| | | | +- startJarLoader@7194b34a | | | | +- startJarLoader@7194b34a
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/resources/ | | | | +- file:/home/user/jetty-distribution-{VERSION}/resources/
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar
| | | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar
| | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b | | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b
| | | | +- file:/home/user/jetty-distribution-@project.version@/start.jar | | | | +- file:/home/user/jetty-distribution-{VERSION}/start.jar
| | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b | | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b
| | | +> org.eclipse.jetty.server.context.ManagedAttributes=QoSFilter,TransparentProxy.ThreadPool,TransparentProxy.HttpClient | | | +> org.eclipse.jetty.server.context.ManagedAttributes=QoSFilter,TransparentProxy.ThreadPool,TransparentProxy.HttpClient
| | | +> context-override-example=a context value | | | +> context-override-example=a context value
| | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any- | | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-
| | | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-continuation-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-servlets-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-api-9.0.2.v20130417.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-servlet-9.0.2.v20130417.jar | | | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-continuation-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-servlets-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-api-9.0.2.v20130417.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/WEB-INF/lib/websocket-servlet-9.0.2.v20130417.jar
| | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$ | | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$
| | | +> QoSFilter=org.eclipse.jetty.servlets.QoSFilter@6df3d1f5 | | | +> QoSFilter=org.eclipse.jetty.servlets.QoSFilter@6df3d1f5
| | | +> com.sun.jsp.taglibraryCache={} | | | +> com.sun.jsp.taglibraryCache={}
@ -550,7 +550,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED | | | | | += jsp@19c47==org.apache.jasper.servlet.JspServlet,0,true - STARTED
| | | | | | +- logVerbosityLevel=DEBUG | | | | | | +- logVerbosityLevel=DEBUG
| | | | | | +- fork=false | | | | | | +- fork=false
| | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-@project.version@/resources:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar:/home/user/jetty-distribution-@project.version@/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib | | | | | | +- com.sun.appserv.jsp.classpath=/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar:/home/user/jetty-distribution-{VERSION}/resources:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar:/home/user/jetty-distribution-{VERSION}/start.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/opt/local/lib/libsvnjavahl-1.0.dylib:/System/Library/Java/Extensions/AppleScriptEngine.jar:/System/Library/Java/Extensions/dns_sd.jar:/System/Library/Java/Extensions/j3daudio.jar:/System/Library/Java/Extensions/j3dcore.jar:/System/Library/Java/Extensions/j3dutils.jar:/System/Library/Java/Extensions/jai_codec.jar:/System/Library/Java/Extensions/jai_core.jar:/System/Library/Java/Extensions/libAppleScriptEngine.jnilib:/System/Library/Java/Extensions/libJ3D.jnilib:/System/Library/Java/Extensions/libJ3DAudio.jnilib:/System/Library/Java/Extensions/libJ3DUtils.jnilib:/System/Library/Java/Extensions/libmlib_jai.jnilib:/System/Library/Java/Extensions/libQTJNative.jnilib:/System/Library/Java/Extensions/mlibwrapper_jai.jar:/System/Library/Java/Extensions/MRJToolkit.jar:/System/Library/Java/Extensions/QTJava.zip:/System/Library/Java/Extensions/vecmath.jar:/usr/lib/java/libjdns_sd.jnilib
| | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/jsp | | | | | | +- scratchdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/jsp
| | | | | | +- xpoweredBy=false | | | | | | +- xpoweredBy=false
| | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp | | | | | +- [*.jsp, *.jspf, *.jspx, *.xsp, *.JSP, *.JSPF, *.JSPX, *.XSP]=>jsp
@ -580,42 +580,42 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| | | | | |
| | +> WebAppClassLoader=Transparent Proxy WebApp@3570713d | | +> WebAppClassLoader=Transparent Proxy WebApp@3570713d
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/classes/ | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/classes/
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-client-@project.version@.jar | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-client-{VERSION}.jar
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-proxy-@project.version@.jar | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-proxy-{VERSION}.jar
| | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar | | | +- file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar
| | | +- startJarLoader@7194b34a | | | +- startJarLoader@7194b34a
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/resources/ | | | +- file:/home/user/jetty-distribution-{VERSION}/resources/
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar
| | | +- file:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar
| | | +- sun.misc.Launcher$AppClassLoader@19d1b44b | | | +- sun.misc.Launcher$AppClassLoader@19d1b44b
| | | +- file:/home/user/jetty-distribution-@project.version@/start.jar | | | +- file:/home/user/jetty-distribution-{VERSION}/start.jar
| | | +- sun.misc.Launcher$ExtClassLoader@1693b52b | | | +- sun.misc.Launcher$ExtClassLoader@1693b52b
| | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any- | | +> javax.servlet.context.tempdir=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-
| | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-client-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-http-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-io-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-proxy-@project.version@.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-util-@project.version@.jar | | +> org.apache.catalina.jsp_classpath=/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/classes:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-client-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-http-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-io-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-proxy-{VERSION}.jar:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/WEB-INF/lib/jetty-util-{VERSION}.jar
| | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$ | | +> org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern=.*/servlet-api-[^/]*\.jar$
| | +> JavadocTransparentProxy.HttpClient=org.eclipse.jetty.client.HttpClient@580f016d | | +> JavadocTransparentProxy.HttpClient=org.eclipse.jetty.client.HttpClient@580f016d
| | +> XrefTransparentProxy.HttpClient=org.eclipse.jetty.client.HttpClient@70c7e52b | | +> XrefTransparentProxy.HttpClient=org.eclipse.jetty.client.HttpClient@70c7e52b
@ -642,7 +642,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| +- org.eclipse.jetty.server.handler.DefaultHandler@4de4926a=org.eclipse.jetty.server.handler:type=defaulthandler,id=0 | +- org.eclipse.jetty.server.handler.DefaultHandler@4de4926a=org.eclipse.jetty.server.handler:type=defaulthandler,id=0
| +- org.eclipse.jetty.server.session.SessionHandler@5c25bf03=org.eclipse.jetty.server.session:context=xref-proxy,type=sessionhandler,id=0 | +- org.eclipse.jetty.server.session.SessionHandler@5c25bf03=org.eclipse.jetty.server.session:context=xref-proxy,type=sessionhandler,id=0
| +- [/ws/*]=>WSChat=org.eclipse.jetty.servlet:context=test,type=servletmapping,name=WSChat,id=0 | +- [/ws/*]=>WSChat=org.eclipse.jetty.servlet:context=test,type=servletmapping,name=WSChat,id=0
| +- o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-@project.version@/webapps/ROOT/,AVAILABLE}{/ROOT}=org.eclipse.jetty.webapp:context=ROOT,type=webappcontext,id=0 | +- o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-{VERSION}/webapps/ROOT/,AVAILABLE}{/ROOT}=org.eclipse.jetty.webapp:context=ROOT,type=webappcontext,id=0
| +- o.e.j.w.WebAppContext@7ea88b1c{/async-rest,[file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/, jar:file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar!/META-INF/resources/],AVAILABLE}{/async-rest.war}=org.eclipse.jetty.webapp:context=async-rest,type=webappcontext,id=0 | +- o.e.j.w.WebAppContext@7ea88b1c{/async-rest,[file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/, jar:file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar!/META-INF/resources/],AVAILABLE}{/async-rest.war}=org.eclipse.jetty.webapp:context=async-rest,type=webappcontext,id=0
| +- ServerConnector@3d0f282{HTTP/1.1}{0.0.0.0:9090}=org.eclipse.jetty.server:context=HTTP/1.1@3d0f282,type=serverconnector,id=0 | +- ServerConnector@3d0f282{HTTP/1.1}{0.0.0.0:9090}=org.eclipse.jetty.server:context=HTTP/1.1@3d0f282,type=serverconnector,id=0
| +- org.eclipse.jetty.security.DefaultAuthenticatorFactory@6242c657=org.eclipse.jetty.security:context=ROOT,type=defaultauthenticatorfactory,id=0 | +- org.eclipse.jetty.security.DefaultAuthenticatorFactory@6242c657=org.eclipse.jetty.security:context=ROOT,type=defaultauthenticatorfactory,id=0
@ -685,7 +685,7 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
| +- [/*]/[]==0=>QoSFilter=org.eclipse.jetty.servlet:context=test,type=filtermapping,name=QoSFilter,id=0 | +- [/*]/[]==0=>QoSFilter=org.eclipse.jetty.servlet:context=test,type=filtermapping,name=QoSFilter,id=0
| +- org.eclipse.jetty.server.session.SessionHandler@5a770658=org.eclipse.jetty.server.session:context=ROOT,type=sessionhandler,id=0 | +- org.eclipse.jetty.server.session.SessionHandler@5a770658=org.eclipse.jetty.server.session:context=ROOT,type=sessionhandler,id=0
| +- org.eclipse.jetty.server.session.SessionHandler@336abd81=org.eclipse.jetty.server.session:context=test,type=sessionhandler,id=0 | +- org.eclipse.jetty.server.session.SessionHandler@336abd81=org.eclipse.jetty.server.session:context=test,type=sessionhandler,id=0
| +- o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-@project.version@/javadoc,AVAILABLE}=org.eclipse.jetty.server.handler:context=javadoc,type=contexthandler,id=0 | +- o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-{VERSION}/javadoc,AVAILABLE}=org.eclipse.jetty.server.handler:context=javadoc,type=contexthandler,id=0
| +- org.eclipse.jetty.servlets.QoSFilter@6df3d1f5=org.eclipse.jetty.servlets:context=test,type=qosfilter,id=0 | +- org.eclipse.jetty.servlets.QoSFilter@6df3d1f5=org.eclipse.jetty.servlets:context=test,type=qosfilter,id=0
| +- [*.more]=>Dump=org.eclipse.jetty.servlet:context=test,type=servletmapping,name=Dump,id=1 | +- [*.more]=>Dump=org.eclipse.jetty.servlet:context=test,type=servletmapping,name=Dump,id=1
| +- Dump@20ae14==com.acme.Dump,1,true=org.eclipse.jetty.servlet:context=test,type=servletholder,name=Dump,id=0 | +- Dump@20ae14==com.acme.Dump,1,true=org.eclipse.jetty.servlet:context=test,type=servletholder,name=Dump,id=0
@ -792,33 +792,33 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
+= org.eclipse.jetty.server.session.HashSessionIdManager@289eb857 - STARTED += org.eclipse.jetty.server.session.HashSessionIdManager@289eb857 - STARTED
| |
+> startJarLoader@7194b34a +> startJarLoader@7194b34a
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-xml-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-xml-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/servlet-api-3.0.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/servlet-api-3.0.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-http-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-http-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-continuation-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-continuation-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-server-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-server-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-security-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-security-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-servlet-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-servlet-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-webapp-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-webapp-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-deploy-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-deploy-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-client-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-client-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-jmx-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-jmx-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/com.sun.el-2.2.0.v201303151357.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/com.sun.el-2.2.0.v201303151357.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.el-2.2.0.v201303151357.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.el-2.2.0.v201303151357.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/javax.servlet.jsp-2.2.0.v201112011158.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.jasper.glassfish-2.2.2.v201112011158.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
+- file:/home/user/jetty-distribution-@project.version@/resources/ +- file:/home/user/jetty-distribution-{VERSION}/resources/
+- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-api-9.0.2.v20130417.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-api-9.0.2.v20130417.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-common-9.0.2.v20130417.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-common-9.0.2.v20130417.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-server-9.0.2.v20130417.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-server-9.0.2.v20130417.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/websocket/websocket-servlet-9.0.2.v20130417.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/websocket/websocket-servlet-9.0.2.v20130417.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-util-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-util-{VERSION}.jar
+- file:/home/user/jetty-distribution-@project.version@/lib/jetty-io-@project.version@.jar +- file:/home/user/jetty-distribution-{VERSION}/lib/jetty-io-{VERSION}.jar
+- sun.misc.Launcher$AppClassLoader@19d1b44b +- sun.misc.Launcher$AppClassLoader@19d1b44b
+- file:/home/user/jetty-distribution-@project.version@/start.jar +- file:/home/user/jetty-distribution-{VERSION}/start.jar
+- sun.misc.Launcher$ExtClassLoader@1693b52b +- sun.misc.Launcher$ExtClassLoader@1693b52b
2013-04-29 14:38:39.422:INFO:oejs.Server:Thread-2: Graceful shutdown org.eclipse.jetty.server.Server@76f08fe1 by Mon Apr 29 14:38:44 CDT 2013 2013-04-29 14:38:39.422:INFO:oejs.Server:Thread-2: Graceful shutdown org.eclipse.jetty.server.Server@76f08fe1 by Mon Apr 29 14:38:44 CDT 2013
2013-04-29 14:38:39.429:INFO:oejs.ServerConnector:Thread-2: Stopped ServerConnector@3d0f282{HTTP/1.1}{0.0.0.0:9090} 2013-04-29 14:38:39.429:INFO:oejs.ServerConnector:Thread-2: Stopped ServerConnector@3d0f282{HTTP/1.1}{0.0.0.0:9090}
@ -826,9 +826,9 @@ org.eclipse.jetty.server.Server@76f08fe1 - STARTING
2013-04-29 14:38:39.444:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@4ac92718{/proxy,file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/,UNAVAILABLE}{/xref-proxy.war} 2013-04-29 14:38:39.444:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@4ac92718{/proxy,file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-xref-proxy.war-_xref-proxy-any-/webapp/,UNAVAILABLE}{/xref-proxy.war}
2013-04-29 14:38:39.447:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged 2013-04-29 14:38:39.447:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged
2013-04-29 14:38:39.447:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@716d9094{/test,file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/,UNAVAILABLE}{/test.war} 2013-04-29 14:38:39.447:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@716d9094{/test,file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-test.war-_test-any-/webapp/,UNAVAILABLE}{/test.war}
2013-04-29 14:38:39.455:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-@project.version@/javadoc,UNAVAILABLE} 2013-04-29 14:38:39.455:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.s.h.ContextHandler@7b2dffdf{/javadoc,file:/home/user/jetty-distribution-{VERSION}/javadoc,UNAVAILABLE}
2013-04-29 14:38:39.456:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged 2013-04-29 14:38:39.456:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged
2013-04-29 14:38:39.456:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-@project.version@/webapps/ROOT/,UNAVAILABLE}{/ROOT} 2013-04-29 14:38:39.456:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@6f01ba6f{/,file:/home/user/jetty-distribution-{VERSION}/webapps/ROOT/,UNAVAILABLE}{/ROOT}
2013-04-29 14:38:39.456:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.s.h.MovedContextHandler@5e0c8d24{/oldContextPath,null,UNAVAILABLE} 2013-04-29 14:38:39.456:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.s.h.MovedContextHandler@5e0c8d24{/oldContextPath,null,UNAVAILABLE}
2013-04-29 14:38:39.457:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged 2013-04-29 14:38:39.457:INFO:oejsl.ELContextCleaner:Thread-2: javax.el.BeanELResolver purged
2013-04-29 14:38:39.457:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@7ea88b1c{/async-rest,[file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/, jar:file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar!/META-INF/resources/],UNAVAILABLE}{/async-rest.war} 2013-04-29 14:38:39.457:INFO:oejsh.ContextHandler:Thread-2: stopped o.e.j.w.WebAppContext@7ea88b1c{/async-rest,[file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/, jar:file:/private/var/folders/br/kbs2g3753c54wmv4j31pnw5r0000gn/T/jetty-0.0.0.0-9090-async-rest.war-_async-rest-any-/webapp/WEB-INF/lib/example-async-rest-jar-9.0.2.v20130417.jar!/META-INF/resources/],UNAVAILABLE}{/async-rest.war}

2
jetty-documentation/src/main/asciidoc/administration/logging/example-apache-log4j.adoc
View File

@ -22,7 +22,7 @@ This is accomplished by configuring Jetty for logging to http://logging.apache.o
A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with log4j. A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with log4j.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

2
jetty-documentation/src/main/asciidoc/administration/logging/example-java-util-logging-native.adoc
View File

@ -32,7 +32,7 @@ ____
A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with `java.util.logging`. A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with `java.util.logging`.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

2
jetty-documentation/src/main/asciidoc/administration/logging/example-java-util-logging.adoc
View File

@ -24,7 +24,7 @@ If you want to use the built-in native `JavaUtilLog` implementation, see #exampl
A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with `java.util.logging`. A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for logging with `java.util.logging`.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

2
jetty-documentation/src/main/asciidoc/administration/logging/example-logback-centralized-logging.adoc
View File

@ -35,7 +35,7 @@ See https://github.com/jetty-project/jetty-webapp-logging/blob/master/src/main/j
A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for capturing all Jetty server logging from multiple logging frameworks into a single logging output file managed by Logback. A convenient replacement `logging` module has been created to bootstrap your `${jetty.base}` directory for capturing all Jetty server logging from multiple logging frameworks into a single logging output file managed by Logback.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

2
jetty-documentation/src/main/asciidoc/administration/logging/example-logback.adoc
View File

@ -22,7 +22,7 @@ This is accomplished by configuring Jetty for logging to `Logback`, which uses h
A convenient replacement `logging` module has been created to bootstrap the `${jetty.base}` directory for logging with logback. A convenient replacement `logging` module has been created to bootstrap the `${jetty.base}` directory for logging with logback.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

2
jetty-documentation/src/main/asciidoc/administration/logging/example-slf4j-multiple-loggers.adoc
View File

@ -86,7 +86,7 @@ It also requires including the other Slf4j binding JARs in the classpath, along
A convenient replacement `logging` module has been created to bootstrap the `${jetty.base}` directory for capturing all Jetty server logging from multiple logging frameworks into a single logging output file managed by logback. A convenient replacement `logging` module has been created to bootstrap the `${jetty.base}` directory for capturing all Jetty server logging from multiple logging frameworks into a single logging output file managed by logback.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ mkdir modules [mybase]$ mkdir modules
[mybase]$ cd modules [mybase]$ cd modules

12
jetty-documentation/src/main/asciidoc/administration/npn/npn.adoc
View File

@ -41,7 +41,7 @@ servlet container); you can use it in any other Java network server.
To enable NPN support, start the JVM as follows: To enable NPN support, start the JVM as follows:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
java -Xbootclasspath/p:<path_to_npn_boot_jar> ... java -Xbootclasspath/p:<path_to_npn_boot_jar> ...
---- ----
@ -89,7 +89,7 @@ below for further details about client and server provider methods.
[[client-example]] [[client-example]]
== Client Example == Client Example
[source,java] [source, java, subs="{sub-order}"]
---- ----
SSLContext sslContext = ...; SSLContext sslContext = ...;
final SSLSocket sslSocket = (SSLSocket)context.getSocketFactory().createSocket("localhost", server.getLocalPort()); final SSLSocket sslSocket = (SSLSocket)context.getSocketFactory().createSocket("localhost", server.getLocalPort());
@ -131,7 +131,7 @@ that the client application can:
The example for SSLEngine is identical, and you just need to replace the The example for SSLEngine is identical, and you just need to replace the
SSLSocket instance with an SSLEngine instance. SSLSocket instance with an SSLEngine instance.
[source,java] [source, java, subs="{sub-order}"]
---- ----
final SSLSocket sslSocket = ...; final SSLSocket sslSocket = ...;
NextProtoNego.put(sslSocket, new NextProtoNego.ServerProvider() NextProtoNego.put(sslSocket, new NextProtoNego.ServerProvider()
@ -196,7 +196,7 @@ You can write and run unit tests that use the NPN implementation. The
solution that we use with Maven is to specify an additional command line solution that we use with Maven is to specify an additional command line
argument to the Surefire plugin: argument to the Surefire plugin:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project> <project>
@ -281,7 +281,7 @@ implementation with the OpenJDK versions.
Clone the OpenJDK repository with the following command: Clone the OpenJDK repository with the following command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ hg clone http://hg.openjdk.java.net/jdk7u/jdk7u jdk7u $ hg clone http://hg.openjdk.java.net/jdk7u/jdk7u jdk7u
$ cd jdk7u $ cd jdk7u
@ -291,7 +291,7 @@ $ ./get_source.sh
To update the source to a specific tag, use the following command: To update the source to a specific tag, use the following command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ ./make/scripts/hgforest.sh update <tag-name> $ ./make/scripts/hgforest.sh update <tag-name>

42
jetty-documentation/src/main/asciidoc/administration/runner/jetty-runner.adoc
View File

@ -33,7 +33,7 @@ You will need the jetty-runner jar:
Let's assume we have a very simple webapp, that does not need any resources from its environment, nor any configuration apart from the defaults. Let's assume we have a very simple webapp, that does not need any resources from its environment, nor any configuration apart from the defaults.
Starting it is as simple as doing the following: Starting it is as simple as doing the following:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar simple.war > java -jar jetty-runner.jar simple.war
.... ....
@ -42,14 +42,14 @@ This will start jetty on port 8080, and deploy the webapp to "/".
Your webapp does not have to be packed into a war, you can deploy a webapp that is a directory instead in the same way: Your webapp does not have to be packed into a war, you can deploy a webapp that is a directory instead in the same way:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar simple > java -jar jetty-runner.jar simple
.... ....
In fact, the webapp does not have to be a war or even a directory, it can simply be a jetty link:#using-context-provider[context xml] file that describes your webapp: In fact, the webapp does not have to be a war or even a directory, it can simply be a jetty link:#using-context-provider[context xml] file that describes your webapp:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar simple-context.xml > java -jar jetty-runner.jar simple-context.xml
.... ....
@ -65,7 +65,7 @@ If you have more than one webapp that must be deployed, simply provide them all
You can control the context paths for them using the "--path" parameter. You can control the context paths for them using the "--path" parameter.
Here's an example of deploying 2 wars (although either or both of them could be unpacked directories instead): Here's an example of deploying 2 wars (although either or both of them could be unpacked directories instead):
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --path /one my1.war --path /two my2.war > java -jar jetty-runner.jar --path /one my1.war --path /two my2.war
.... ....
@ -73,7 +73,7 @@ Here's an example of deploying 2 wars (although either or both of them could be
If you have context xml files that describe your webapps, you can fully configure your webapps in them, and hence you don't need to use the command line switches. If you have context xml files that describe your webapps, you can fully configure your webapps in them, and hence you don't need to use the command line switches.
Just provide the list of context files like so: Just provide the list of context files like so:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar my-first-context.xml my-second-context.xml my-third-context.xml > java -jar jetty-runner.jar my-first-context.xml my-second-context.xml my-third-context.xml
@ -91,7 +91,7 @@ By default the jetty-runner will listen on port 8080.
You can easily change this on the command line using the "--port" command. You can easily change this on the command line using the "--port" command.
Here's an example that runs our simple.war on port 9090: Here's an example that runs our simple.war on port 9090:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --port 9090 simple.war > java -jar jetty-runner.jar --port 9090 simple.war
.... ....
@ -101,7 +101,7 @@ Here's an example that runs our simple.war on port 9090:
Instead of, or in addition to using command line switches, you can use one or more jetty.xml files to configure the environment for your webapps. Instead of, or in addition to using command line switches, you can use one or more jetty.xml files to configure the environment for your webapps.
Here's an example where we apply two different jetty.xml files: Here's an example where we apply two different jetty.xml files:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --config jetty.xml --config jetty-https.xml simple.war > java -jar jetty-runner.jar --config jetty.xml --config jetty-https.xml simple.war
.... ....
@ -115,14 +115,14 @@ ____
You can see the fill set of configuration options using the --help switch: You can see the fill set of configuration options using the --help switch:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --help > java -jar jetty-runner.jar --help
.... ....
Here's what the output will look like: Here's what the output will look like:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Usage: java [-Djetty.home=dir] -jar jetty-runner.jar [--help|--version] [ server opts] [[ context opts] context ...] Usage: java [-Djetty.home=dir] -jar jetty-runner.jar [--help|--version] [ server opts] [[ context opts] context ...]
@ -147,7 +147,7 @@ Context opts:
Printing the version::: Printing the version:::
Print out the version of jetty and then exit immediately. Print out the version of jetty and then exit immediately.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --version > java -jar jetty-runner.jar --version
@ -158,7 +158,7 @@ Configuring a request log:::
If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over. If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over.
Note that for finer grained configuration of the link:{JDURL}/org/eclipse/jetty/server/NCSARequestLog.html[request log], you will need to use a jetty xml file instead. Note that for finer grained configuration of the link:{JDURL}/org/eclipse/jetty/server/NCSARequestLog.html[request log], you will need to use a jetty xml file instead.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --log yyyy_mm_dd-requests.log my.war > java -jar jetty-runner.jar --log yyyy_mm_dd-requests.log my.war
@ -168,7 +168,7 @@ Configuring the output log:::
Redirect the output of jetty logging to the named file. Redirect the output of jetty logging to the named file.
If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over. If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --out yyyy_mm_dd-output.log my.war > java -jar jetty-runner.jar --out yyyy_mm_dd-output.log my.war
@ -178,7 +178,7 @@ Configuring the interface for http:::
Like jetty standalone, the default is for the connectors to listen on all interfaces on a machine. Like jetty standalone, the default is for the connectors to listen on all interfaces on a machine.
You can control that by specifying the name or ip address of the particular interface you wish to use with the --host argument: You can control that by specifying the name or ip address of the particular interface you wish to use with the --host argument:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --host 192.168.22.19 my.war > java -jar jetty-runner.jar --host 192.168.22.19 my.war
@ -188,7 +188,7 @@ Configuring the port for http:::
The default port number is 8080. The default port number is 8080.
To link:#how-to-configure-connectors[configure a https connector], use a jetty xml config file instead. To link:#how-to-configure-connectors[configure a https connector], use a jetty xml config file instead.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --port 9090 my.war > java -jar jetty-runner.jar --port 9090 my.war
@ -199,7 +199,7 @@ Configuring stop:::
This requires the use of a "secret" key, to prevent malicious or accidental termination. This requires the use of a "secret" key, to prevent malicious or accidental termination.
Use the --stop-port and --stop-key parameters as arguments to the jetty-runner: Use the --stop-port and --stop-key parameters as arguments to the jetty-runner:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --stop-port 8181 --stop-key abc123 > java -jar jetty-runner.jar --stop-port 8181 --stop-key abc123
@ -209,7 +209,7 @@ Then, to stop jetty from a different terminal, you need to supply the same port
For this you'll either need a local installation of jetty, the link:#jetty-maven-plugin[jetty-maven-plugin], the link:#jetty-ant[jetty-ant plugin], or write a custom class. For this you'll either need a local installation of jetty, the link:#jetty-maven-plugin[jetty-maven-plugin], the link:#jetty-ant[jetty-ant plugin], or write a custom class.
Here's how to use a jetty installation to perform a stop: Here's how to use a jetty installation to perform a stop:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar start.jar --stop-port 8181 --stop-key abc123 --stop > java -jar start.jar --stop-port 8181 --stop-key abc123 --stop
@ -222,7 +222,7 @@ Configuring the container classpath:::
--lib adds the location of a directory which contains jars to add to the container classpath. --lib adds the location of a directory which contains jars to add to the container classpath.
You can add 1 or more. Here's an example of configuring 2 directories: You can add 1 or more. Here's an example of configuring 2 directories:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --lib /usr/local/external/lib --lib $HOME/external-other/lib my.war > java -jar jetty-runner.jar --lib /usr/local/external/lib --lib $HOME/external-other/lib my.war
@ -232,7 +232,7 @@ You can add 1 or more. Here's an example of configuring 2 directories:
You can add 1 or more. You can add 1 or more.
Here's an example of configuring 3 extra jars: Here's an example of configuring 3 extra jars:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --jar /opt/stuff/jars/jar1.jar --jar $HOME/jars/jar2.jar --jar /usr/local/proj/jars/jar3.jar my.war > java -jar jetty-runner.jar --jar /opt/stuff/jars/jar1.jar --jar $HOME/jars/jar2.jar --jar /usr/local/proj/jars/jar3.jar my.war
@ -242,7 +242,7 @@ Here's an example of configuring 3 extra jars:
You can add 1 or more. You can add 1 or more.
Here's an example of configuring a single extra classes dir: Here's an example of configuring a single extra classes dir:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --classes /opt/stuff/classes my.war > java -jar jetty-runner.jar --classes /opt/stuff/classes my.war
@ -254,7 +254,7 @@ Gathering statistics:::
context with a password. Here's an example of enabling statistics, context with a password. Here's an example of enabling statistics,
with no password protection: with no password protection:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --stats unsecure my.war > java -jar jetty-runner.jar --stats unsecure my.war
@ -276,7 +276,7 @@ digest: MD5:6e120743ad67abfbc385bc2bb754e297,user
+ +
Assuming we've copied it into the local directory, we would apply it like so Assuming we've copied it into the local directory, we would apply it like so
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -jar jetty-runner.jar --stats realm.properties my.war > java -jar jetty-runner.jar --stats realm.properties my.war

6
jetty-documentation/src/main/asciidoc/administration/sessions/session-clustering-gcloud-datastore.adoc
View File

@ -48,7 +48,7 @@ To do that, you can use `--skip-file-validation=glcoud-sessions` argument to sta
The gcloud-sessions module will have installed file called `${jetty.home}/etc/jetty-gcloud-sessions.xml`. The gcloud-sessions module will have installed file called `${jetty.home}/etc/jetty-gcloud-sessions.xml`.
This file configures an instance of the `GCloudSessionIdManager` that will be shared across all webapps deployed on that server. It looks like this: This file configures an instance of the `GCloudSessionIdManager` that will be shared across all webapps deployed on that server. It looks like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-gcloud/jetty-gcloud-session-manager/src/main/config/etc/jetty-gcloud-sessions.xml[] include::{SRCDIR}/jetty-gcloud/jetty-gcloud-session-manager/src/main/config/etc/jetty-gcloud-sessions.xml[]
---- ----
@ -106,7 +106,7 @@ The basic difference is how you get a reference to the Jetty `org.eclipse.jetty.
From a context xml file, you reference the Server instance as a Ref: From a context xml file, you reference the Server instance as a Ref:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Get a reference to the GCloudSessionIdManager --> <!-- Get a reference to the GCloudSessionIdManager -->
<Ref id="Server"> <Ref id="Server">
@ -130,7 +130,7 @@ From a context xml file, you reference the Server instance as a Ref:
From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly: From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Reference the server directly --> <!-- Reference the server directly -->
<Get name="server"> <Get name="server">

6
jetty-documentation/src/main/asciidoc/administration/sessions/session-clustering-infinispan.adoc
View File

@ -63,7 +63,7 @@ The Infinispan module will have installed file called `$\{jetty.home}/etc/jetty-
This file configures an instance of the `InfinispanSessionIdManager` that will be shared across all webapps deployed on that server. This file configures an instance of the `InfinispanSessionIdManager` that will be shared across all webapps deployed on that server.
It looks like this: It looks like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-infinispan/src/main/config/etc/jetty-infinispan.xml[] include::{SRCDIR}/jetty-infinispan/src/main/config/etc/jetty-infinispan.xml[]
---- ----
@ -89,7 +89,7 @@ The basic difference is how you get a reference to the Jetty `org.eclipse.jetty.
From a context xml file, you reference the Server instance as a Ref: From a context xml file, you reference the Server instance as a Ref:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Expose the jetty infinispan classes for session serialization --> <!-- Expose the jetty infinispan classes for session serialization -->
<Call name="prependServerClass"> <Call name="prependServerClass">
@ -128,7 +128,7 @@ From a context xml file, you reference the Server instance as a Ref:
From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly: From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Expose the jetty infinispan classes for session serialization --> <!-- Expose the jetty infinispan classes for session serialization -->
<Call name="prependServerClass"> <Call name="prependServerClass">

16
jetty-documentation/src/main/asciidoc/administration/sessions/session-clustering-jdbc.adoc
View File

@ -44,7 +44,7 @@ When using the jetty distribution, to enable jdbc session persistence, you will
You will also find the following properties, either in your base's start.d/jdbc-session.ini file or appended to your start.ini, depending on how you enabled the module: You will also find the following properties, either in your base's start.d/jdbc-session.ini file or appended to your start.ini, depending on how you enabled the module:
[source,java] [source, java, subs="{sub-order}"]
---- ----
## Unique identifier for this node in the cluster ## Unique identifier for this node in the cluster
jetty.jdbcSession.workerName=node1 jetty.jdbcSession.workerName=node1
@ -78,7 +78,7 @@ The jdbc-session module will have installed file called `$\{jetty.home}/etc/jett
This file configures an instance of the `JDBCSessionIdManager` that will be shared across all webapps deployed on that server. This file configures an instance of the `JDBCSessionIdManager` that will be shared across all webapps deployed on that server.
It looks like this: It looks like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-server/src/main/config/etc/jetty-jdbc-sessions.xml[] include::{SRCDIR}/jetty-server/src/main/config/etc/jetty-jdbc-sessions.xml[]
---- ----
@ -87,7 +87,7 @@ As well as uncommenting and setting up appropriate values for the properties dis
As Jetty configuration files are direct mappings of XML to Java, it is straight forward to do this in code: As Jetty configuration files are direct mappings of XML to Java, it is straight forward to do this in code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(); Server server = new Server();
... ...
@ -127,7 +127,7 @@ These classes have getter/setter methods for the table name and all columns.
Here's an example of changing the name of `JettySessionsId` table and its single column. Here's an example of changing the name of `JettySessionsId` table and its single column.
This example will use java code, but as explained above, you may also do this via a Jetty xml configuration file: This example will use java code, but as explained above, you may also do this via a Jetty xml configuration file:
[source,java] [source, java, subs="{sub-order}"]
---- ----
JDBCSessionIdManager idManager = new JDBCSessionIdManager(server); JDBCSessionIdManager idManager = new JDBCSessionIdManager(server);
@ -140,7 +140,7 @@ idManager.setSessionIdTableSchema(idTableSchema);
In a similar fashion, you can change the names of the table and columns for the `JettySessions` table. In a similar fashion, you can change the names of the table and columns for the `JettySessions` table.
*Note* that both the `SessionIdTableSchema` and the `SessionTableSchema` instances are set on the `JDBCSessionIdManager` class. *Note* that both the `SessionIdTableSchema` and the `SessionTableSchema` instances are set on the `JDBCSessionIdManager` class.
[source,java] [source, java, subs="{sub-order}"]
---- ----
JDBCSessionIdManager idManager = new JDBCSessionIdManager(server); JDBCSessionIdManager idManager = new JDBCSessionIdManager(server);
@ -170,7 +170,7 @@ The basic difference is how you get a reference to the Jetty `org.eclipse.jetty.
From a context xml file, you reference the Server instance as a Ref: From a context xml file, you reference the Server instance as a Ref:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Ref id="Server"> <Ref id="Server">
<Call id="idMgr" name="getSessionIdManager"/> <Call id="idMgr" name="getSessionIdManager"/>
@ -190,7 +190,7 @@ From a context xml file, you reference the Server instance as a Ref:
From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly: From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Get name="server"> <Get name="server">
@ -211,7 +211,7 @@ From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance direc
If you're embedding this in code: If you're embedding this in code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
//assuming you have already set up the JDBCSessionIdManager as shown earlier //assuming you have already set up the JDBCSessionIdManager as shown earlier

14
jetty-documentation/src/main/asciidoc/administration/sessions/session-clustering-mongodb.adoc
View File

@ -51,7 +51,7 @@ To do that, you can use `--skip-file-validation=nosql` argument to start.jar on
You will also find the following properties, either in your base's `start.d/nosql.ini` file or appended to your `start.ini`, depending on how you enabled the module: You will also find the following properties, either in your base's `start.d/nosql.ini` file or appended to your `start.ini`, depending on how you enabled the module:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
## Unique identifier for this node in the cluster ## Unique identifier for this node in the cluster
jetty.nosqlSession.workerName=node1 jetty.nosqlSession.workerName=node1
@ -75,7 +75,7 @@ The nosql module will have installed file called `$\{jetty.home}/etc/jetty-nosql
This file configures an instance of the `MongoSessionIdManager` that will be shared across all webapps deployed on that server. This file configures an instance of the `MongoSessionIdManager` that will be shared across all webapps deployed on that server.
It looks like this: It looks like this:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-nosql/src/main/config/etc/jetty-nosql.xml[] include::{SRCDIR}/jetty-nosql/src/main/config/etc/jetty-nosql.xml[]
---- ----
@ -84,7 +84,7 @@ The `MongoSessionIdManager` needs access to a MongoDB cluster, and the `jetty-no
If you need to configure something else, you will need to edit this file. If you need to configure something else, you will need to edit this file.
Here's an example of a more complex setup to use a remote MongoDB instance: Here's an example of a more complex setup to use a remote MongoDB instance:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="mongodb" class="com.mongodb.Mongo"> <New id="mongodb" class="com.mongodb.Mongo">
<Arg> <Arg>
@ -128,7 +128,7 @@ Here's an example of a more complex setup to use a remote MongoDB instance:
As Jetty configuration files are direct mappings of XML to Java, it is straight forward to do this in code: As Jetty configuration files are direct mappings of XML to Java, it is straight forward to do this in code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Server server = new Server(); Server server = new Server();
@ -184,7 +184,7 @@ The basic difference is how you get a reference to the Jetty `org.eclipse.jetty.
From a context xml file, you reference the Server instance as a Ref: From a context xml file, you reference the Server instance as a Ref:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Ref name="Server" id="Server"> <Ref name="Server" id="Server">
<Call id="mongoIdMgr" name="getSessionIdManager"/> <Call id="mongoIdMgr" name="getSessionIdManager"/>
@ -205,7 +205,7 @@ From a context xml file, you reference the Server instance as a Ref:
From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly: From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance directly:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Get name="server"> <Get name="server">
<Get id="mongoIdMgr" name="sessionIdManager"/> <Get id="mongoIdMgr" name="sessionIdManager"/>
@ -225,7 +225,7 @@ From a `WEB-INF/jetty-web.xml` file, you can reference the Server instance direc
If you're embedding this in code: If you're embedding this in code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
//assuming you have already set up the MongoSessionIdManager as shown earlier //assuming you have already set up the MongoSessionIdManager as shown earlier
//and have a reference to the Server instance: //and have a reference to the Server instance:

18
jetty-documentation/src/main/asciidoc/administration/sessions/setting-session-characteristics.adoc
View File

@ -72,7 +72,7 @@ The following sections provide examples of how to apply the init parameters.
You can set these parameters as context parameters in a web application's `WEB-INF/web.xml` file: You can set these parameters as context parameters in a web application's `WEB-INF/web.xml` file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
@ -101,7 +101,7 @@ You can set these parameters as context parameters in a web application's `WEB-I
You can configure init parameters on a web application, either in code, or in a Jetty context xml file equivalent: You can configure init parameters on a web application, either in code, or in a Jetty context xml file equivalent:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -128,7 +128,7 @@ You can configure init parameters on a web application, either in code, or in a
You can configure init parameters directly on a `SessionManager` instance, either in code or the equivalent in xml: You can configure init parameters directly on a `SessionManager` instance, either in code or the equivalent in xml:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -163,7 +163,7 @@ For full details, consult the http://docs.oracle.com/javaee/6/api/javax/servlet/
Below is an example of this implementation: a `ServletContextListener` retrieves the `SessionCookieConfig` and sets up some new values when the context is being initialized: Below is an example of this implementation: a `ServletContextListener` retrieves the `SessionCookieConfig` and sets up some new values when the context is being initialized:
[source,java] [source, java, subs="{sub-order}"]
---- ----
import javax.servlet.SessionCookieConfig; import javax.servlet.SessionCookieConfig;
import javax.servlet.ServletContextEvent; import javax.servlet.ServletContextEvent;
@ -203,7 +203,7 @@ public class TestListener implements ServletContextListener
You can also use `web.xml` to configure the session handling characteristics instead: here's an example doing exactly the same as above instead of using code: You can also use `web.xml` to configure the session handling characteristics instead: here's an example doing exactly the same as above instead of using code:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<web-app <web-app
@ -234,7 +234,7 @@ In addition to the configuration of link:#session-cookie-configuration[session c
To determine what are the _default_ session tracking characteristics used by the container, call: To determine what are the _default_ session tracking characteristics used by the container, call:
[source,java] [source, java, subs="{sub-order}"]
---- ----
javax.servlet.SessionContext.getDefaultSessionTrackingModes(); javax.servlet.SessionContext.getDefaultSessionTrackingModes();
---- ----
@ -247,21 +247,21 @@ _default_ session tracking modes for Jetty are:
To see which session tracking modes are actually in effect for this Context, the following call returns a `java.util.Set` of `javax.servlet.SessionTrackingMode`: To see which session tracking modes are actually in effect for this Context, the following call returns a `java.util.Set` of `javax.servlet.SessionTrackingMode`:
[source,java] [source, java, subs="{sub-order}"]
---- ----
javax.servlet.SessionContext.getEffectiveSessionTrackingModes(); javax.servlet.SessionContext.getEffectiveSessionTrackingModes();
---- ----
To change the session tracking modes, call: To change the session tracking modes, call:
[source,java] [source, java, subs="{sub-order}"]
---- ----
javax.servlet.SessionContext.setSessionTrackingModes(Set<SessionTrackingMode>); javax.servlet.SessionContext.setSessionTrackingModes(Set<SessionTrackingMode>);
---- ----
You may also set the tracking mode in `web.xml`, e.g.: You may also set the tracking mode in `web.xml`, e.g.:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<web-app <web-app

6
jetty-documentation/src/main/asciidoc/administration/sessions/using-persistent-sessions.adoc
View File

@ -29,7 +29,7 @@ A `SessionManager` does just what its name suggests – it manages the lifecycle
Each webapp must have its own unique `SessionManager` instance. Each webapp must have its own unique `SessionManager` instance.
Enabling persistence is as simple as configuring the `HashSessionManager` as the `SessionManager` for a webapp and telling it where on disk to store the sessions: Enabling persistence is as simple as configuring the `HashSessionManager` as the `SessionManager` for a webapp and telling it where on disk to store the sessions:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -73,7 +73,7 @@ For example, the Wicket web framework requires the servlet environment to be ava
Using `SessionManager.setLazyLoad(true)`, Jetty loads sessions lazily either when it receives the first request for a session, or the session scavenger runs for the first time, whichever happens first. Using `SessionManager.setLazyLoad(true)`, Jetty loads sessions lazily either when it receives the first request for a session, or the session scavenger runs for the first time, whichever happens first.
Here's how the configuration looks in XML: Here's how the configuration looks in XML:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Set name="sessionHandler"> <Set name="sessionHandler">
<New class="org.eclipse.jetty.server.session.SessionHandler"> <New class="org.eclipse.jetty.server.session.SessionHandler">
@ -91,7 +91,7 @@ Here's how the configuration looks in XML:
To enable session persistence for the Jetty Maven plugin, set up the `HashSessionManager` in the configuration section like so: To enable session persistence for the Jetty Maven plugin, set up the `HashSessionManager` in the configuration section like so:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<plugin> <plugin>
<groupId>org.eclipse.jetty</groupId> <groupId>org.eclipse.jetty</groupId>

4
jetty-documentation/src/main/asciidoc/administration/startup/screen-empty-base-listconfig.adoc
View File

@ -14,7 +14,7 @@
// You may elect to redistribute this code under either of these licenses. // You may elect to redistribute this code under either of these licenses.
// ======================================================================== // ========================================================================
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ java -jar /opt/jetty-distribution/start.jar --list-config [mybase]$ java -jar /opt/jetty-distribution/start.jar --list-config
@ -34,7 +34,7 @@ Java Environment:
Jetty Environment: Jetty Environment:
----------------- -----------------
jetty.version = @project.version@ jetty.version = {VERSION}
jetty.home = /opt/jetty-distribution jetty.home = /opt/jetty-distribution
jetty.base = /home/jetty/mybase jetty.base = /home/jetty/mybase

2
jetty-documentation/src/main/asciidoc/administration/startup/screen-empty-base.adoc
View File

@ -14,7 +14,7 @@
// You may elect to redistribute this code under either of these licenses. // You may elect to redistribute this code under either of these licenses.
// ======================================================================== // ========================================================================
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
WARNING: Nothing to start, exiting ... WARNING: Nothing to start, exiting ...

22
jetty-documentation/src/main/asciidoc/administration/startup/screen-http-webapp-deploy-listconfig.adoc
View File

@ -14,7 +14,7 @@
// You may elect to redistribute this code under either of these licenses. // You may elect to redistribute this code under either of these licenses.
// ======================================================================== // ========================================================================
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ java -jar /opt/jetty-distribution/start.jar --list-config [mybase]$ java -jar /opt/jetty-distribution/start.jar --list-config
@ -34,7 +34,7 @@ Java Environment:
Jetty Environment: Jetty Environment:
----------------- -----------------
jetty.version = @project.version@ jetty.version = {VERSION}
jetty.home = /opt/jetty-distribution jetty.home = /opt/jetty-distribution
jetty.base = /home/jetty/mybase jetty.base = /home/jetty/mybase
@ -64,15 +64,15 @@ Note: order presented here is how they would appear on the classpath.
changes to the --module=name command line options will be reflected here. changes to the --module=name command line options will be reflected here.
0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar 0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
1: 3.1.0.M0 | ${jetty.home}/lib/jetty-schemas-3.1.jar 1: 3.1.0.M0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
2: @project.version@ | ${jetty.home}/lib/jetty-http-@project.version@.jar 2: {VERSION} | ${jetty.home}/lib/jetty-http-{VERSION}.jar
3: @project.version@ | ${jetty.home}/lib/jetty-server-@project.version@.jar 3: {VERSION} | ${jetty.home}/lib/jetty-server-{VERSION}.jar
4: @project.version@ | ${jetty.home}/lib/jetty-xml-@project.version@.jar 4: {VERSION} | ${jetty.home}/lib/jetty-xml-{VERSION}.jar
5: @project.version@ | ${jetty.home}/lib/jetty-util-@project.version@.jar 5: {VERSION} | ${jetty.home}/lib/jetty-util-{VERSION}.jar
6: @project.version@ | ${jetty.home}/lib/jetty-io-@project.version@.jar 6: {VERSION} | ${jetty.home}/lib/jetty-io-{VERSION}.jar
7: @project.version@ | ${jetty.home}/lib/jetty-security-@project.version@.jar 7: {VERSION} | ${jetty.home}/lib/jetty-security-{VERSION}.jar
8: @project.version@ | ${jetty.home}/lib/jetty-servlet-@project.version@.jar 8: {VERSION} | ${jetty.home}/lib/jetty-servlet-{VERSION}.jar
9: @project.version@ | ${jetty.home}/lib/jetty-webapp-@project.version@.jar 9: {VERSION} | ${jetty.home}/lib/jetty-webapp-{VERSION}.jar
10: @project.version@ | ${jetty.home}/lib/jetty-deploy-@project.version@.jar 10: {VERSION} | ${jetty.home}/lib/jetty-deploy-{VERSION}.jar
Jetty Active XMLs: Jetty Active XMLs:
------------------ ------------------

2
jetty-documentation/src/main/asciidoc/administration/startup/screen-http-webapp-deploy.adoc
View File

@ -14,7 +14,7 @@
// You may elect to redistribute this code under either of these licenses. // You may elect to redistribute this code under either of these licenses.
// ======================================================================== // ========================================================================
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ java -jar /opt/jetty-distribution/start.jar --add-to-start=http,webapp,deploy [mybase]$ java -jar /opt/jetty-distribution/start.jar --add-to-start=http,webapp,deploy

2
jetty-documentation/src/main/asciidoc/administration/startup/screen-list-modules.adoc
View File

@ -14,7 +14,7 @@
// You may elect to redistribute this code under either of these licenses. // You may elect to redistribute this code under either of these licenses.
// ======================================================================== // ========================================================================
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[mybase]$ java -jar /opt/jetty-distribution/start.jar --list-modules [mybase]$ java -jar /opt/jetty-distribution/start.jar --list-modules

8
jetty-documentation/src/main/asciidoc/administration/startup/start-jar.adoc
View File

@ -21,10 +21,10 @@ The most basic way of starting the Jetty standalone server is to execute
the `start.jar`, which is a bootstrap for starting Jetty with the the `start.jar`, which is a bootstrap for starting Jetty with the
configuration you want. configuration you want.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ java -jar start.jar [jetty-distribution-{VERSION}]$ java -jar start.jar
2013-09-23 11:27:06.654:INFO:oejs.Server:main: jetty-@project.version@ 2013-09-23 11:27:06.654:INFO:oejs.Server:main: jetty-{VERSION}
... ...
.... ....
@ -175,7 +175,7 @@ module system).
http://graphviz.org/content/dot-language[dot file] of the module graph http://graphviz.org/content/dot-language[dot file] of the module graph
as it exists for the active `${jetty.base}`. as it exists for the active `${jetty.base}`.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# generate module.dot # generate module.dot
$ java -jar start.jar --module=websocket --write-module-graph=modules.dot $ java -jar start.jar --module=websocket --write-module-graph=modules.dot

106
jetty-documentation/src/main/asciidoc/administration/startup/startup-base-vs-home.adoc
View File

@ -61,9 +61,9 @@ enables the various demonstration webapps and server configurations.
How to use the demo-base directory as a Jetty Base directory. How to use the demo-base directory as a Jetty Base directory.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ ls -la [jetty-distribution-{VERSION}]$ ls -la
total 496 total 496
drwxrwxr-x 11 user group 4096 Oct 8 15:23 ./ drwxrwxr-x 11 user group 4096 Oct 8 15:23 ./
drwxr-xr-x 14 user group 4096 Oct 8 13:04 ../ drwxr-xr-x 14 user group 4096 Oct 8 13:04 ../
@ -82,11 +82,11 @@ drwxrwxr-x 2 user group 4096 Oct 8 06:54 start.d/
-rw-rw-r-- 1 user group 71921 Sep 30 19:55 start.jar -rw-rw-r-- 1 user group 71921 Sep 30 19:55 start.jar
-rw-rw-r-- 1 user group 336468 Sep 30 19:55 VERSION.txt -rw-rw-r-- 1 user group 336468 Sep 30 19:55 VERSION.txt
drwxrwxr-x 2 user group 4096 Oct 8 06:54 webapps/ drwxrwxr-x 2 user group 4096 Oct 8 06:54 webapps/
[jetty-distribution-@project.version@]$ cd demo-base [jetty-distribution-{VERSION}]$ cd demo-base
[demo-base]$ java -jar $JETTY_HOME/start.jar [demo-base]$ java -jar $JETTY_HOME/start.jar
2013-10-16 09:08:47.800:WARN::main: demo test-realm is deployed. DO NOT USE IN PRODUCTION! 2013-10-16 09:08:47.800:WARN::main: demo test-realm is deployed. DO NOT USE IN PRODUCTION!
2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-@project.version@ 2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-{VERSION}
2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/jetty-distribution-@project.version@/demo-base/webapps/] at interval 1 2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/jetty-distribution-{VERSION}/demo-base/webapps/] at interval 1
2013-10-16 09:08:48.072:WARN::main: async-rest webapp is deployed. DO NOT USE IN PRODUCTION! 2013-10-16 09:08:48.072:WARN::main: async-rest webapp is deployed. DO NOT USE IN PRODUCTION!
... ...
.... ....
@ -97,7 +97,7 @@ using the Jetty Base concepts.
If you want to see what the Jetty Base looks like without executing If you want to see what the Jetty Base looks like without executing
Jetty, you can simply list the configuration Jetty, you can simply list the configuration
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar $JETTY_HOME/start.jar --list-config [my-base]$ java -jar $JETTY_HOME/start.jar --list-config
@ -114,9 +114,9 @@ Java Environment:
Jetty Environment: Jetty Environment:
----------------- -----------------
jetty.home=/home/user/jetty-distribution-@project.version@ jetty.home=/home/user/jetty-distribution-{VERSION}
jetty.base=/home/user/jetty-distribution-@project.version@/demo-base jetty.base=/home/user/jetty-distribution-{VERSION}/demo-base
jetty.version=@project.version@ jetty.version={VERSION}
JVM Arguments: JVM Arguments:
-------------- --------------
@ -124,8 +124,8 @@ JVM Arguments:
System Properties: System Properties:
------------------ ------------------
jetty.base = /home/user/jetty-distribution-@project.version@/demo-base jetty.base = /home/user/jetty-distribution-{VERSION}/demo-base
jetty.home = /home/user/jetty-distribution-@project.version@ jetty.home = /home/user/jetty-distribution-{VERSION}
Properties: Properties:
----------- -----------
@ -152,26 +152,26 @@ Jetty Server Classpath:
Version Information on 42 entries in the classpath. Version Information on 42 entries in the classpath.
Note: order presented here is how they would appear on the classpath. Note: order presented here is how they would appear on the classpath.
changes to the --module=name command line options will be reflected here. changes to the --module=name command line options will be reflected here.
0: @project.version@ | ${jetty.home}/lib/jetty-client-@project.version@.jar 0: {VERSION} | ${jetty.home}/lib/jetty-client-{VERSION}.jar
1: 1.4.1.v201005082020 | ${jetty.base}/lib/ext/javax.mail.glassfish-1.4.1.v201005082020.jar 1: 1.4.1.v201005082020 | ${jetty.base}/lib/ext/javax.mail.glassfish-1.4.1.v201005082020.jar
2: @project.version@ | ${jetty.base}/lib/ext/test-mock-resources-@project.version@.jar 2: {VERSION} | ${jetty.base}/lib/ext/test-mock-resources-{VERSION}.jar
3: (dir) | ${jetty.home}/resources 3: (dir) | ${jetty.home}/resources
4: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar 4: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
5: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar 5: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
6: @project.version@ | ${jetty.home}/lib/jetty-http-@project.version@.jar 6: {VERSION} | ${jetty.home}/lib/jetty-http-{VERSION}.jar
7: @project.version@ | ${jetty.home}/lib/jetty-continuation-@project.version@.jar 7: {VERSION} | ${jetty.home}/lib/jetty-continuation-{VERSION}.jar
8: @project.version@ | ${jetty.home}/lib/jetty-server-@project.version@.jar 8: {VERSION} | ${jetty.home}/lib/jetty-server-{VERSION}.jar
9: @project.version@ | ${jetty.home}/lib/jetty-xml-@project.version@.jar 9: {VERSION} | ${jetty.home}/lib/jetty-xml-{VERSION}.jar
10: @project.version@ | ${jetty.home}/lib/jetty-util-@project.version@.jar 10: {VERSION} | ${jetty.home}/lib/jetty-util-{VERSION}.jar
11: @project.version@ | ${jetty.home}/lib/jetty-io-@project.version@.jar 11: {VERSION} | ${jetty.home}/lib/jetty-io-{VERSION}.jar
12: @project.version@ | ${jetty.home}/lib/jetty-jaas-@project.version@.jar 12: {VERSION} | ${jetty.home}/lib/jetty-jaas-{VERSION}.jar
13: @project.version@ | ${jetty.home}/lib/jetty-jndi-@project.version@.jar 13: {VERSION} | ${jetty.home}/lib/jetty-jndi-{VERSION}.jar
14: 1.1.0.v201105071233 | ${jetty.home}/lib/jndi/javax.activation-1.1.0.v201105071233.jar 14: 1.1.0.v201105071233 | ${jetty.home}/lib/jndi/javax.activation-1.1.0.v201105071233.jar
15: 1.4.1.v201005082020 | ${jetty.home}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar 15: 1.4.1.v201005082020 | ${jetty.home}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar
16: 1.2 | ${jetty.home}/lib/jndi/javax.transaction-api-1.2.jar 16: 1.2 | ${jetty.home}/lib/jndi/javax.transaction-api-1.2.jar
17: @project.version@ | ${jetty.home}/lib/jetty-rewrite-@project.version@.jar 17: {VERSION} | ${jetty.home}/lib/jetty-rewrite-{VERSION}.jar
18: @project.version@ | ${jetty.home}/lib/jetty-security-@project.version@.jar 18: {VERSION} | ${jetty.home}/lib/jetty-security-{VERSION}.jar
19: @project.version@ | ${jetty.home}/lib/jetty-servlet-@project.version@.jar 19: {VERSION} | ${jetty.home}/lib/jetty-servlet-{VERSION}.jar
20: 3.0.0 | ${jetty.home}/lib/jsp/javax.el-3.0.0.jar 20: 3.0.0 | ${jetty.home}/lib/jsp/javax.el-3.0.0.jar
21: 1.2.0.v201105211821 | ${jetty.home}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar 21: 1.2.0.v201105211821 | ${jetty.home}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
22: 2.3.2 | ${jetty.home}/lib/jsp/javax.servlet.jsp-2.3.2.jar 22: 2.3.2 | ${jetty.home}/lib/jsp/javax.servlet.jsp-2.3.2.jar
@ -179,21 +179,21 @@ Note: order presented here is how they would appear on the classpath.
24: 2.3.3 | ${jetty.home}/lib/jsp/jetty-jsp-jdt-2.3.3.jar 24: 2.3.3 | ${jetty.home}/lib/jsp/jetty-jsp-jdt-2.3.3.jar
25: 1.2.0.v201112081803 | ${jetty.home}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar 25: 1.2.0.v201112081803 | ${jetty.home}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
26: 3.8.2.v20130121-145325 | ${jetty.home}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar 26: 3.8.2.v20130121-145325 | ${jetty.home}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
27: @project.version@ | ${jetty.home}/lib/jetty-plus-@project.version@.jar 27: {VERSION} | ${jetty.home}/lib/jetty-plus-{VERSION}.jar
28: @project.version@ | ${jetty.home}/lib/jetty-webapp-@project.version@.jar 28: {VERSION} | ${jetty.home}/lib/jetty-webapp-{VERSION}.jar
29: @project.version@ | ${jetty.home}/lib/jetty-annotations-@project.version@.jar 29: {VERSION} | ${jetty.home}/lib/jetty-annotations-{VERSION}.jar
30: 4.1 | ${jetty.home}/lib/annotations/asm-4.1.jar 30: 4.1 | ${jetty.home}/lib/annotations/asm-4.1.jar
31: 4.1 | ${jetty.home}/lib/annotations/asm-commons-4.1.jar 31: 4.1 | ${jetty.home}/lib/annotations/asm-commons-4.1.jar
32: 1.2 | ${jetty.home}/lib/annotations/javax.annotation-api-1.2.jar 32: 1.2 | ${jetty.home}/lib/annotations/javax.annotation-api-1.2.jar
33: @project.version@ | ${jetty.home}/lib/jetty-deploy-@project.version@.jar 33: {VERSION} | ${jetty.home}/lib/jetty-deploy-{VERSION}.jar
34: 1.0 | ${jetty.home}/lib/websocket/javax.websocket-api-1.0.jar 34: 1.0 | ${jetty.home}/lib/websocket/javax.websocket-api-1.0.jar
35: @project.version@ | ${jetty.home}/lib/websocket/javax-websocket-client-impl-@project.version@.jar 35: {VERSION} | ${jetty.home}/lib/websocket/javax-websocket-client-impl-{VERSION}.jar
36: @project.version@ | ${jetty.home}/lib/websocket/javax-websocket-server-impl-@project.version@.jar 36: {VERSION} | ${jetty.home}/lib/websocket/javax-websocket-server-impl-{VERSION}.jar
37: @project.version@ | ${jetty.home}/lib/websocket/websocket-api-@project.version@.jar 37: {VERSION} | ${jetty.home}/lib/websocket/websocket-api-{VERSION}.jar
38: @project.version@ | ${jetty.home}/lib/websocket/websocket-client-@project.version@.jar 38: {VERSION} | ${jetty.home}/lib/websocket/websocket-client-{VERSION}.jar
39: @project.version@ | ${jetty.home}/lib/websocket/websocket-common-@project.version@.jar 39: {VERSION} | ${jetty.home}/lib/websocket/websocket-common-{VERSION}.jar
40: @project.version@ | ${jetty.home}/lib/websocket/websocket-server-@project.version@.jar 40: {VERSION} | ${jetty.home}/lib/websocket/websocket-server-{VERSION}.jar
41: @project.version@ | ${jetty.home}/lib/websocket/websocket-servlet-@project.version@.jar 41: {VERSION} | ${jetty.home}/lib/websocket/websocket-servlet-{VERSION}.jar
Jetty Active XMLs: Jetty Active XMLs:
------------------ ------------------
@ -223,7 +223,7 @@ elements came from, be it in either in `${jetty.home}` or
If you look at the $\{jetty.base}/start.ini you will see something like If you look at the $\{jetty.base}/start.ini you will see something like
the following. the following.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ cat start.ini [my-base]$ cat start.ini
# Enable security via jaas, and configure it # Enable security via jaas, and configure it
@ -282,14 +282,14 @@ The Jetty start.jar and XML files always assume that both
You can opt to manually define the `${jetty.home}` and `${jetty.base}` You can opt to manually define the `${jetty.home}` and `${jetty.base}`
directories, such as this: directories, such as this:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ pwd [jetty-distribution-{VERSION}]$ pwd
/home/user/jetty-distribution-@project.version@ /home/user/jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ java -jar start.jar \ [jetty-distribution-{VERSION}]$ java -jar start.jar \
jetty.home=/home/user/jetty-distribution-@project.version@ \ jetty.home=/home/user/jetty-distribution-{VERSION} \
jetty.base=/home/user/my-base jetty.base=/home/user/my-base
2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-@project.version@ 2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-{VERSION}
2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1 2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1
... ...
.... ....
@ -300,12 +300,12 @@ The following example uses default discovery of `${jetty.home}` by using
the parent directory of wherever start.jar itself is, and a manual the parent directory of wherever start.jar itself is, and a manual
declaration of `${jetty.base}`. declaration of `${jetty.base}`.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ pwd [jetty-distribution-{VERSION}]$ pwd
/home/user/jetty-distribution-@project.version@ /home/user/jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ java -jar start.jar jetty.base=/home/user/my-base [jetty-distribution-{VERSION}]$ java -jar start.jar jetty.base=/home/user/my-base
2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-@project.version@ 2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-{VERSION}
2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1 2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1
... ...
.... ....
@ -318,13 +318,13 @@ The following demonstrates this by allowing default discovery of
`${jetty.home}` via locating the `start.jar`, and using the `user.dir` `${jetty.home}` via locating the `start.jar`, and using the `user.dir`
System Property for `${jetty.base}`. System Property for `${jetty.base}`.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ pwd [jetty-distribution-{VERSION}]$ pwd
/home/user/jetty-distribution-@project.version@ /home/user/jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ cd /home/user/my-base [jetty-distribution-{VERSION}]$ cd /home/user/my-base
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar
2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-@project.version@ 2013-10-16 09:08:47.802:INFO:oejs.Server:main: jetty-{VERSION}
2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1 2013-10-16 09:08:47.817:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1
... ...
.... ....

50
jetty-documentation/src/main/asciidoc/administration/startup/startup-classpath.adoc
View File

@ -67,7 +67,7 @@ The `--list-classpath` command line option is used as such.
(Demonstrated with the link:#demo-base[demo-base from the Jetty (Demonstrated with the link:#demo-base[demo-base from the Jetty
Distribution]) Distribution])
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[demo-base]$ java -jar $JETTY_HOME/start.jar --list-classpath [demo-base]$ java -jar $JETTY_HOME/start.jar --list-classpath
@ -76,26 +76,26 @@ Jetty Server Classpath:
Version Information on 42 entries in the classpath. Version Information on 42 entries in the classpath.
Note: order presented here is how they would appear on the classpath. Note: order presented here is how they would appear on the classpath.
changes to the --module=name command line options will be reflected here. changes to the --module=name command line options will be reflected here.
0: @project.version@ | ${jetty.home}/lib/jetty-client-@project.version@.jar 0: {VERSION} | ${jetty.home}/lib/jetty-client-{VERSION}.jar
1: 1.4.1.v201005082020 | ${jetty.base}/lib/ext/javax.mail.glassfish-1.4.1.v201005082020.jar 1: 1.4.1.v201005082020 | ${jetty.base}/lib/ext/javax.mail.glassfish-1.4.1.v201005082020.jar
2: @project.version@ | ${jetty.base}/lib/ext/test-mock-resources-@project.version@.jar 2: {VERSION} | ${jetty.base}/lib/ext/test-mock-resources-{VERSION}.jar
3: (dir) | ${jetty.home}/resources 3: (dir) | ${jetty.home}/resources
4: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar 4: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
5: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar 5: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
6: @project.version@ | ${jetty.home}/lib/jetty-http-@project.version@.jar 6: {VERSION} | ${jetty.home}/lib/jetty-http-{VERSION}.jar
7: @project.version@ | ${jetty.home}/lib/jetty-continuation-@project.version@.jar 7: {VERSION} | ${jetty.home}/lib/jetty-continuation-{VERSION}.jar
8: @project.version@ | ${jetty.home}/lib/jetty-server-@project.version@.jar 8: {VERSION} | ${jetty.home}/lib/jetty-server-{VERSION}.jar
9: @project.version@ | ${jetty.home}/lib/jetty-xml-@project.version@.jar 9: {VERSION} | ${jetty.home}/lib/jetty-xml-{VERSION}.jar
10: @project.version@ | ${jetty.home}/lib/jetty-util-@project.version@.jar 10: {VERSION} | ${jetty.home}/lib/jetty-util-{VERSION}.jar
11: @project.version@ | ${jetty.home}/lib/jetty-io-@project.version@.jar 11: {VERSION} | ${jetty.home}/lib/jetty-io-{VERSION}.jar
12: @project.version@ | ${jetty.home}/lib/jetty-jaas-@project.version@.jar 12: {VERSION} | ${jetty.home}/lib/jetty-jaas-{VERSION}.jar
13: @project.version@ | ${jetty.home}/lib/jetty-jndi-@project.version@.jar 13: {VERSION} | ${jetty.home}/lib/jetty-jndi-{VERSION}.jar
14: 1.1.0.v201105071233 | ${jetty.home}/lib/jndi/javax.activation-1.1.0.v201105071233.jar 14: 1.1.0.v201105071233 | ${jetty.home}/lib/jndi/javax.activation-1.1.0.v201105071233.jar
15: 1.4.1.v201005082020 | ${jetty.home}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar 15: 1.4.1.v201005082020 | ${jetty.home}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar
16: 1.2 | ${jetty.home}/lib/jndi/javax.transaction-api-1.2.jar 16: 1.2 | ${jetty.home}/lib/jndi/javax.transaction-api-1.2.jar
17: @project.version@ | ${jetty.home}/lib/jetty-rewrite-@project.version@.jar 17: {VERSION} | ${jetty.home}/lib/jetty-rewrite-{VERSION}.jar
18: @project.version@ | ${jetty.home}/lib/jetty-security-@project.version@.jar 18: {VERSION} | ${jetty.home}/lib/jetty-security-{VERSION}.jar
19: @project.version@ | ${jetty.home}/lib/jetty-servlet-@project.version@.jar 19: {VERSION} | ${jetty.home}/lib/jetty-servlet-{VERSION}.jar
20: 3.0.0 | ${jetty.home}/lib/jsp/javax.el-3.0.0.jar 20: 3.0.0 | ${jetty.home}/lib/jsp/javax.el-3.0.0.jar
21: 1.2.0.v201105211821 | ${jetty.home}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar 21: 1.2.0.v201105211821 | ${jetty.home}/lib/jsp/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
22: 2.3.2 | ${jetty.home}/lib/jsp/javax.servlet.jsp-2.3.2.jar 22: 2.3.2 | ${jetty.home}/lib/jsp/javax.servlet.jsp-2.3.2.jar
@ -103,21 +103,21 @@ Note: order presented here is how they would appear on the classpath.
24: 2.3.3 | ${jetty.home}/lib/jsp/jetty-jsp-jdt-2.3.3.jar 24: 2.3.3 | ${jetty.home}/lib/jsp/jetty-jsp-jdt-2.3.3.jar
25: 1.2.0.v201112081803 | ${jetty.home}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar 25: 1.2.0.v201112081803 | ${jetty.home}/lib/jsp/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
26: 3.8.2.v20130121-145325 | ${jetty.home}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar 26: 3.8.2.v20130121-145325 | ${jetty.home}/lib/jsp/org.eclipse.jdt.core-3.8.2.v20130121.jar
27: @project.version@ | ${jetty.home}/lib/jetty-plus-@project.version@.jar 27: {VERSION} | ${jetty.home}/lib/jetty-plus-{VERSION}.jar
28: @project.version@ | ${jetty.home}/lib/jetty-webapp-@project.version@.jar 28: {VERSION} | ${jetty.home}/lib/jetty-webapp-{VERSION}.jar
29: @project.version@ | ${jetty.home}/lib/jetty-annotations-@project.version@.jar 29: {VERSION} | ${jetty.home}/lib/jetty-annotations-{VERSION}.jar
30: 4.1 | ${jetty.home}/lib/annotations/asm-4.1.jar 30: 4.1 | ${jetty.home}/lib/annotations/asm-4.1.jar
31: 4.1 | ${jetty.home}/lib/annotations/asm-commons-4.1.jar 31: 4.1 | ${jetty.home}/lib/annotations/asm-commons-4.1.jar
32: 1.2 | ${jetty.home}/lib/annotations/javax.annotation-api-1.2.jar 32: 1.2 | ${jetty.home}/lib/annotations/javax.annotation-api-1.2.jar
33: @project.version@ | ${jetty.home}/lib/jetty-deploy-@project.version@.jar 33: {VERSION} | ${jetty.home}/lib/jetty-deploy-{VERSION}.jar
34: 1.0 | ${jetty.home}/lib/websocket/javax.websocket-api-1.0.jar 34: 1.0 | ${jetty.home}/lib/websocket/javax.websocket-api-1.0.jar
35: @project.version@ | ${jetty.home}/lib/websocket/javax-websocket-client-impl-@project.version@.jar 35: {VERSION} | ${jetty.home}/lib/websocket/javax-websocket-client-impl-{VERSION}.jar
36: @project.version@ | ${jetty.home}/lib/websocket/javax-websocket-server-impl-@project.version@.jar 36: {VERSION} | ${jetty.home}/lib/websocket/javax-websocket-server-impl-{VERSION}.jar
37: @project.version@ | ${jetty.home}/lib/websocket/websocket-api-@project.version@.jar 37: {VERSION} | ${jetty.home}/lib/websocket/websocket-api-{VERSION}.jar
38: @project.version@ | ${jetty.home}/lib/websocket/websocket-client-@project.version@.jar 38: {VERSION} | ${jetty.home}/lib/websocket/websocket-client-{VERSION}.jar
39: @project.version@ | ${jetty.home}/lib/websocket/websocket-common-@project.version@.jar 39: {VERSION} | ${jetty.home}/lib/websocket/websocket-common-{VERSION}.jar
40: @project.version@ | ${jetty.home}/lib/websocket/websocket-server-@project.version@.jar 40: {VERSION} | ${jetty.home}/lib/websocket/websocket-server-{VERSION}.jar
41: @project.version@ | ${jetty.home}/lib/websocket/websocket-servlet-@project.version@.jar 41: {VERSION} | ${jetty.home}/lib/websocket/websocket-servlet-{VERSION}.jar
.... ....
Of note is that an attempt is made to list the internally declared Of note is that an attempt is made to list the internally declared

60
jetty-documentation/src/main/asciidoc/administration/startup/startup-overview.adoc
View File

@ -87,10 +87,10 @@ XML Files::
The simplest way to start Jetty is via the `start.jar` mechanism using The simplest way to start Jetty is via the `start.jar` mechanism using
the following Java command line: the following Java command line:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[user]$ cd jetty-distribution-@project.version@ [user]$ cd jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ java -jar start.jar --module=http jetty.http.port=8080 [jetty-distribution-{VERSION}]$ java -jar start.jar --module=http jetty.http.port=8080
.... ....
This command uses the `start.jar` mechanism to bootstrap the classpath, This command uses the `start.jar` mechanism to bootstrap the classpath,
@ -98,9 +98,9 @@ properties, and XML files with the metadata obtained from the `http`
module. Specifically the `http` module is defined in the module. Specifically the `http` module is defined in the
`${jetty.home}/modules/http.mod` file, and includes the following: `${jetty.home}/modules/http.mod` file, and includes the following:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ cat modules/http.mod [jetty-distribution-{VERSION}]$ cat modules/http.mod
[depend] [depend]
server server
@ -121,9 +121,9 @@ section is not actually used by the command above, so the
Following the server dependency, the `${jetty.home}/modules/server.mod` Following the server dependency, the `${jetty.home}/modules/server.mod`
file includes: file includes:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ cat modules/server.mod [jetty-distribution-{VERSION}]$ cat modules/server.mod
[lib] [lib]
lib/servlet-api-3.1.jar lib/servlet-api-3.1.jar
lib/jetty-http-${jetty.version}.jar lib/jetty-http-${jetty.version}.jar
@ -148,9 +148,9 @@ line required to start Jetty.
Another way to see this is by asking Jetty what its configuration looks Another way to see this is by asking Jetty what its configuration looks
like: like:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[jetty-distribution-@project.version@]$ java -jar start.jar --module=http jetty.http.port=9099 --list-config [jetty-distribution-{VERSION}]$ java -jar start.jar --module=http jetty.http.port=9099 --list-config
Java Environment: Java Environment:
----------------- -----------------
@ -165,9 +165,9 @@ Java Environment:
Jetty Environment: Jetty Environment:
----------------- -----------------
jetty.home=/opt/jetty/jetty-distribution-@project.version@ jetty.home=/opt/jetty/jetty-distribution-{VERSION}
jetty.base=/opt/jetty/jetty-distribution-@project.version@ jetty.base=/opt/jetty/jetty-distribution-{VERSION}
jetty.version=@project.version@ jetty.version={VERSION}
JVM Arguments: JVM Arguments:
-------------- --------------
@ -175,8 +175,8 @@ JVM Arguments:
System Properties: System Properties:
------------------ ------------------
jetty.home = /opt/jetty/jetty-distribution-@project.version@ jetty.home = /opt/jetty/jetty-distribution-{VERSION}
jetty.base = /opt/jetty/jetty-distribution-@project.version@ jetty.base = /opt/jetty/jetty-distribution-{VERSION}
Properties: Properties:
----------- -----------
@ -189,11 +189,11 @@ Note: order presented here is how they would appear on the classpath.
changes to the --module=name command line options will be reflected here. changes to the --module=name command line options will be reflected here.
0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar 0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
1: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar 1: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
2: @project.version@ | ${jetty.home}/lib/jetty-http-@project.version@.jar 2: {VERSION} | ${jetty.home}/lib/jetty-http-{VERSION}.jar
3: @project.version@ | ${jetty.home}/lib/jetty-server-@project.version@.jar 3: {VERSION} | ${jetty.home}/lib/jetty-server-{VERSION}.jar
4: @project.version@ | ${jetty.home}/lib/jetty-xml-@project.version@.jar 4: {VERSION} | ${jetty.home}/lib/jetty-xml-{VERSION}.jar
5: @project.version@ | ${jetty.home}/lib/jetty-util-@project.version@.jar 5: {VERSION} | ${jetty.home}/lib/jetty-util-{VERSION}.jar
6: @project.version@ | ${jetty.home}/lib/jetty-io-@project.version@.jar 6: {VERSION} | ${jetty.home}/lib/jetty-io-{VERSION}.jar
Jetty Active XMLs: Jetty Active XMLs:
------------------ ------------------
@ -210,14 +210,14 @@ using a traditional Java command line.
The following is the equivalent `java` command line for what the The following is the equivalent `java` command line for what the
`start.jar` bootstrap above performs. `start.jar` bootstrap above performs.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[user]$ cd jetty-distribution-@project.version@ [user]$ cd jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ echo jetty.http.port=8080 > /tmp/jetty.properties [jetty-distribution-{VERSION}]$ echo jetty.http.port=8080 > /tmp/jetty.properties
[jetty-distribution-@project.version@]$ export JETTY_HOME=`pwd` [jetty-distribution-{VERSION}]$ export JETTY_HOME=`pwd`
[jetty-distribution-@project.version@]$ export JETTY_BASE=`pwd` [jetty-distribution-{VERSION}]$ export JETTY_BASE=`pwd`
[jetty-distribution-@project.version@]$ export JETTY_VERSION="${project.version}" [jetty-distribution-{VERSION}]$ export JETTY_VERSION="${project.version}"
[jetty-distribution-@project.version@]$ java -Djetty.home=$JETTY_HOME \ [jetty-distribution-{VERSION}]$ java -Djetty.home=$JETTY_HOME \
-Djetty.base=$JETTY_BASE \ -Djetty.base=$JETTY_BASE \
-cp \ -cp \
$JETTY_HOME/lib/servlet-api-3.1.jar\ $JETTY_HOME/lib/servlet-api-3.1.jar\
@ -242,10 +242,10 @@ You can further simplify the startup of this server by using the INI
template defined by the modules to create a `start.ini` file with the template defined by the modules to create a `start.ini` file with the
command: command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[user]$ cd jetty-distribution-@project.version@ [user]$ cd jetty-distribution-{VERSION}
[jetty-distribution-@project.version@]$ mkdir example-base [jetty-distribution-{VERSION}]$ mkdir example-base
[example-base]$ cd example-base [example-base]$ cd example-base
[example-base]$ ls -la [example-base]$ ls -la
total 8 total 8
@ -266,7 +266,7 @@ drwxrwxr-x 12 user webgroup 4096 Oct 4 11:49 ../
Once complete, you can edit the `start.ini` file to modify any Once complete, you can edit the `start.ini` file to modify any
parameters and you can run the server with the simple command: parameters and you can run the server with the simple command:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[example-base]$ java -jar $JETTY_HOME/start.jar [example-base]$ java -jar $JETTY_HOME/start.jar
.... ....

68
jetty-documentation/src/main/asciidoc/administration/startup/startup-unix-service.adoc
View File

@ -27,27 +27,27 @@ This script is suitable for setting up Jetty as a service in Unix.
The minimum steps to get Jetty to run as a Service The minimum steps to get Jetty to run as a Service
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[/opt/jetty]# tar -zxf /home/user/downloads/jetty-distribution-@project.version@.tar.gz [/opt/jetty]# tar -zxf /home/user/downloads/jetty-distribution-{VERSION}.tar.gz
[/opt/jetty]# cd jetty-distribution-@project.version@/ [/opt/jetty]# cd jetty-distribution-{VERSION}/
[/opt/jetty/jetty-distribution-@project.version@]# ls [/opt/jetty/jetty-distribution-{VERSION}]# ls
bin lib modules resources start.jar bin lib modules resources start.jar
demo-base license-eplv10-aslv20.html notice.html start.d VERSION.txt demo-base license-eplv10-aslv20.html notice.html start.d VERSION.txt
etc logs README.TXT start.ini webapps etc logs README.TXT start.ini webapps
[/opt/jetty/jetty-distribution-@project.version@]# cp bin/jetty.sh /etc/init.d/jetty [/opt/jetty/jetty-distribution-{VERSION}]# cp bin/jetty.sh /etc/init.d/jetty
[/opt/jetty/jetty-distribution-@project.version@]# echo JETTY_HOME=`pwd` > /etc/default/jetty [/opt/jetty/jetty-distribution-{VERSION}]# echo JETTY_HOME=`pwd` > /etc/default/jetty
[/opt/jetty/jetty-distribution-@project.version@]# cat /etc/default/jetty [/opt/jetty/jetty-distribution-{VERSION}]# cat /etc/default/jetty
JETTY_HOME=/opt/jetty/jetty-distribution-@project.version@ JETTY_HOME=/opt/jetty/jetty-distribution-{VERSION}
[/opt/jetty/jetty-distribution-@project.version@]# service jetty start [/opt/jetty/jetty-distribution-{VERSION}]# service jetty start
Starting Jetty: OK Wed Nov 20 10:26:53 MST 2013 Starting Jetty: OK Wed Nov 20 10:26:53 MST 2013
.... ....
From this simple demonstration we can see that Jetty started From this simple demonstration we can see that Jetty started
successfully as a Unix Service from the successfully as a Unix Service from the
`/opt/jetty/jetty-distribution-@project.version@` directory. `/opt/jetty/jetty-distribution-{VERSION}` directory.
This looks all fine and dandy, however you are running a default Jetty This looks all fine and dandy, however you are running a default Jetty
on the root user id. on the root user id.
@ -62,7 +62,7 @@ The techniques outlined here assume an installation on Linux
Prepare some empty directories to work with. Prepare some empty directories to work with.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# mkdir -p /opt/jetty # mkdir -p /opt/jetty
# mkdir -p /opt/web/mybase # mkdir -p /opt/web/mybase
@ -89,7 +89,7 @@ The directory purposes are as follows:
Jetty $\{project.version} requires Java 7 (or greater) to run. Make sure Jetty $\{project.version} requires Java 7 (or greater) to run. Make sure
you have it installed. you have it installed.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# apt-get install openjdk-7-jdk # apt-get install openjdk-7-jdk
.... ....
@ -97,7 +97,7 @@ you have it installed.
Or download Java 7 from: Or download Java 7 from:
http://www.oracle.com/technetwork/java/javase/downloads/index.html http://www.oracle.com/technetwork/java/javase/downloads/index.html
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# java -version # java -version
java version "1.6.0_27" java version "1.6.0_27"
@ -129,7 +129,7 @@ OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
It is recommended that you create a user to specifically run Jetty. This It is recommended that you create a user to specifically run Jetty. This
user should have the minimum set of privileges needed to run Jetty. user should have the minimum set of privileges needed to run Jetty.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# useradd --user-group --shell /bin/false --home-dir /opt/jetty/temp jetty # useradd --user-group --shell /bin/false --home-dir /opt/jetty/temp jetty
.... ....
@ -143,11 +143,11 @@ link:#jetty-downloading[Official Eclipse Download Site]
Unpack it into place. Unpack it into place.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[/opt/jetty]# tar -zxf /home/user/Downloads/jetty-distribution-@project.version@.tar.gz [/opt/jetty]# tar -zxf /home/user/Downloads/jetty-distribution-{VERSION}.tar.gz
[/opt/jetty]# ls -F [/opt/jetty]# ls -F
jetty-distribution-@project.version@/ jetty-distribution-{VERSION}/
[/opt/jetty]# mkdir /opt/jetty/temp [/opt/jetty]# mkdir /opt/jetty/temp
.... ....
@ -171,11 +171,11 @@ ____
In past versions of Jetty, you would configure / modify / add to the jetty-distribution directory directly. While this is still supported, we encourage you to setup a proper `${jetty.base}` directory, as it will benefit you with easier jetty-distribution upgrades in the future. In past versions of Jetty, you would configure / modify / add to the jetty-distribution directory directly. While this is still supported, we encourage you to setup a proper `${jetty.base}` directory, as it will benefit you with easier jetty-distribution upgrades in the future.
____ ____
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# cd /opt/web/mybase/ # cd /opt/web/mybase/
[/opt/web/mybase]# ls [/opt/web/mybase]# ls
[/opt/web/mybase]# java -jar /opt/jetty/jetty-distribution-@project.version@/start.jar \ [/opt/web/mybase]# java -jar /opt/jetty/jetty-distribution-{VERSION}/start.jar \
--add-to-start=deploy,http,logging --add-to-start=deploy,http,logging
WARNING: deploy initialised in ${jetty.base}/start.ini (appended) WARNING: deploy initialised in ${jetty.base}/start.ini (appended)
WARNING: deploy enabled in ${jetty.base}/start.ini WARNING: deploy enabled in ${jetty.base}/start.ini
@ -211,7 +211,7 @@ up and configuring a `${jetty.base}` directory.
Copy your war file into place. Copy your war file into place.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# cp /home/user/projects/mywebsite.war /opt/web/mybase/webapps/ # cp /home/user/projects/mywebsite.war /opt/web/mybase/webapps/
.... ....
@ -223,7 +223,7 @@ your opportunity to change this from the default value of `8080` to
Edit the `/opt/web/mybase/start.ini` and change the `jetty.http.port` Edit the `/opt/web/mybase/start.ini` and change the `jetty.http.port`
value. value.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# grep jetty.http.port /opt/web/mybase/start.ini # grep jetty.http.port /opt/web/mybase/start.ini
jetty.port=80 jetty.port=80
@ -232,7 +232,7 @@ jetty.port=80
Change the permissions on the Jetty distribution, and your webapp Change the permissions on the Jetty distribution, and your webapp
directories so that the user you created can access it. directories so that the user you created can access it.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# chown --recursive jetty /opt/jetty # chown --recursive jetty /opt/jetty
# chown --recursive jetty /opt/web/mybase # chown --recursive jetty /opt/web/mybase
@ -241,53 +241,53 @@ directories so that the user you created can access it.
Next we need to make the Unix System aware that we have a new Jetty Next we need to make the Unix System aware that we have a new Jetty
Service that can be managed by the standard `service` calls. Service that can be managed by the standard `service` calls.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# cp /opt/jetty/jetty-distribution-@project.version@/bin/jetty.sh /etc/init.d/jetty # cp /opt/jetty/jetty-distribution-{VERSION}/bin/jetty.sh /etc/init.d/jetty
# echo "JETTY_HOME=/opt/jetty/jetty-distribution-@project.version@" > /etc/default/jetty # echo "JETTY_HOME=/opt/jetty/jetty-distribution-{VERSION}" > /etc/default/jetty
# echo "JETTY_BASE=/opt/web/mybase" >> /etc/default/jetty # echo "JETTY_BASE=/opt/web/mybase" >> /etc/default/jetty
# echo "TMPDIR=/opt/jetty/temp" >> /etc/default/jetty # echo "TMPDIR=/opt/jetty/temp" >> /etc/default/jetty
.... ....
Test out the configuration Test out the configuration
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# service jetty status # service jetty status
Checking arguments to Jetty: Checking arguments to Jetty:
START_INI = /opt/web/mybase/start.ini START_INI = /opt/web/mybase/start.ini
JETTY_HOME = /opt/jetty/jetty-distribution-@project.version@ JETTY_HOME = /opt/jetty/jetty-distribution-{VERSION}
JETTY_BASE = /opt/web/mybase JETTY_BASE = /opt/web/mybase
JETTY_CONF = /opt/jetty/jetty-distribution-@project.version@/etc/jetty.conf JETTY_CONF = /opt/jetty/jetty-distribution-{VERSION}/etc/jetty.conf
JETTY_PID = /var/run/jetty.pid JETTY_PID = /var/run/jetty.pid
JETTY_START = /opt/jetty/jetty-distribution-@project.version@/start.jar JETTY_START = /opt/jetty/jetty-distribution-{VERSION}/start.jar
JETTY_LOGS = /opt/web/mybase/logs JETTY_LOGS = /opt/web/mybase/logs
CLASSPATH = CLASSPATH =
JAVA = /usr/bin/java JAVA = /usr/bin/java
JAVA_OPTIONS = -Djetty.state=/opt/web/mybase/jetty.state JAVA_OPTIONS = -Djetty.state=/opt/web/mybase/jetty.state
-Djetty.logs=/opt/web/mybase/logs -Djetty.logs=/opt/web/mybase/logs
-Djetty.home=/opt/jetty/jetty-distribution-@project.version@ -Djetty.home=/opt/jetty/jetty-distribution-{VERSION}
-Djetty.base=/opt/web/mybase -Djetty.base=/opt/web/mybase
-Djava.io.tmpdir=/opt/jetty/temp -Djava.io.tmpdir=/opt/jetty/temp
JETTY_ARGS = jetty-logging.xml jetty-started.xml JETTY_ARGS = jetty-logging.xml jetty-started.xml
RUN_CMD = /usr/bin/java RUN_CMD = /usr/bin/java
-Djetty.state=/opt/web/mybase/jetty.state -Djetty.state=/opt/web/mybase/jetty.state
-Djetty.logs=/opt/web/mybase/logs -Djetty.logs=/opt/web/mybase/logs
-Djetty.home=/opt/jetty/jetty-distribution-@project.version@ -Djetty.home=/opt/jetty/jetty-distribution-{VERSION}
-Djetty.base=/opt/web/mybase -Djetty.base=/opt/web/mybase
-Djava.io.tmpdir=/opt/jetty/temp -Djava.io.tmpdir=/opt/jetty/temp
-jar /opt/jetty/jetty-distribution-@project.version@/start.jar -jar /opt/jetty/jetty-distribution-{VERSION}/start.jar
jetty-logging.xml jetty-logging.xml
jetty-started.xml jetty-started.xml
.... ....
You now have a configured `${jetty.base}` in `/opt/web/mybase` and a You now have a configured `${jetty.base}` in `/opt/web/mybase` and a
jetty-distribution in `/opt/jetty/jetty-distribution-@project.version@`, jetty-distribution in `/opt/jetty/jetty-distribution-{VERSION}`,
along with the service level files necessary to start the service. along with the service level files necessary to start the service.
Go ahead, start it. Go ahead, start it.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
# service jetty start # service jetty start
Starting Jetty: OK Wed Nov 20 12:35:28 MST 2013 Starting Jetty: OK Wed Nov 20 12:35:28 MST 2013

14
jetty-documentation/src/main/asciidoc/administration/startup/startup-windows-service.adoc
View File

@ -29,7 +29,7 @@ The techniques outlined here are based on Windows 7 (64-bit), using JDK
Prepare some empty directories to work with. Prepare some empty directories to work with.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\> mkdir opt C:\> mkdir opt
C:\> cd opt C:\> cd opt
@ -78,7 +78,7 @@ C:\opt\temp::
Or download Java 7 from: Or download Java 7 from:
http://www.oracle.com/technetwork/java/javase/downloads/index.html http://www.oracle.com/technetwork/java/javase/downloads/index.html
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\opt>java -version C:\opt>java -version
java version "1.7.0_45" java version "1.7.0_45"
@ -90,13 +90,13 @@ Grab a copy of the ZIP distribution from the
link:#jetty-downloading[Official Eclipse Download Site] link:#jetty-downloading[Official Eclipse Download Site]
Open it up the downloaded Zip in Windows Explorer and drag the contents Open it up the downloaded Zip in Windows Explorer and drag the contents
of the `jetty-distribution-@project.version@` directory into place at of the `jetty-distribution-{VERSION}` directory into place at
`C:\opt\jetty` `C:\opt\jetty`
Once you are complete, the contents of the `C:\opt\jetty` directory Once you are complete, the contents of the `C:\opt\jetty` directory
should look like this: should look like this:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\opt\jetty>dir C:\opt\jetty>dir
Volume in drive C has no label. Volume in drive C has no label.
@ -143,7 +143,7 @@ file.
Once you are complete, the contents of `C:\opt` directory should look Once you are complete, the contents of `C:\opt` directory should look
like this: like this:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\opt> dir C:\opt> dir
Volume in drive C has no label. Volume in drive C has no label.
@ -168,7 +168,7 @@ your WebApps and the configurations that they need.
We'll start by specifying which modules we want to use (this will create We'll start by specifying which modules we want to use (this will create
a start.ini file and also create a few empty directories for you) a start.ini file and also create a few empty directories for you)
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\opt\myappbase>java -jar ..\jetty\start.jar --add-to-start=deploy,http,logging C:\opt\myappbase>java -jar ..\jetty\start.jar --add-to-start=deploy,http,logging
@ -221,7 +221,7 @@ up and configuring a `${jetty.base}` directory.
At this point you merely have to copy your WAR files into the webapps At this point you merely have to copy your WAR files into the webapps
directory. directory.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
C:\opt\myappbase> copy C:\projects\mywebsite.war webapps\ C:\opt\myappbase> copy C:\projects\mywebsite.war webapps\
.... ....

12
jetty-documentation/src/main/asciidoc/administration/tuning/high-load.adoc
View File

@ -50,7 +50,7 @@ Linux does a reasonable job of self-configuring TCP/IP, but there are a few limi
You should increase TCP buffer sizes to at least 16MB for 10G paths and tune the auto-tuning (although you now need to consider buffer bloat). You should increase TCP buffer sizes to at least 16MB for 10G paths and tune the auto-tuning (although you now need to consider buffer bloat).
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl -w net.core.rmem_max=16777216 $ sysctl -w net.core.rmem_max=16777216
$ sysctl -w net.core.wmem_max=16777216 $ sysctl -w net.core.wmem_max=16777216
@ -65,7 +65,7 @@ $ sysctl -w net.ipv4.tcp_wmem="4096 16384 16777216"
The default value is 128; if you are running a high-volume server and connections are getting refused at a TCP level, you need to increase this. The default value is 128; if you are running a high-volume server and connections are getting refused at a TCP level, you need to increase this.
This is a very tweakable setting in such a case: if you set it too high, resource problems occur as it tries to notify a server of a large number of connections, and many remain pending, but if you set it too low, refused connections occur. This is a very tweakable setting in such a case: if you set it too high, resource problems occur as it tries to notify a server of a large number of connections, and many remain pending, but if you set it too low, refused connections occur.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl -w net.core.somaxconn=4096 $ sysctl -w net.core.somaxconn=4096
@ -74,7 +74,7 @@ This is a very tweakable setting in such a case: if you set it too high, resourc
The `net.core.netdev_max_backlog` controls the size of the incoming packet queue for upper-layer (java) processing. The `net.core.netdev_max_backlog` controls the size of the incoming packet queue for upper-layer (java) processing.
The default (2048) may be increased and other related parameters (TODO MORE EXPLANATION) adjusted with: The default (2048) may be increased and other related parameters (TODO MORE EXPLANATION) adjusted with:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl -w net.core.netdev_max_backlog=16384 $ sysctl -w net.core.netdev_max_backlog=16384
@ -88,7 +88,7 @@ $ sysctl -w net.ipv4.tcp_syncookies=1
If many outgoing connections are made (for example, on load generators), the operating system might run low on ports. Thus it is best to increase the port range, and allow reuse of sockets in TIME_WAIT: If many outgoing connections are made (for example, on load generators), the operating system might run low on ports. Thus it is best to increase the port range, and allow reuse of sockets in TIME_WAIT:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl -w net.ipv4.ip_local_port_range="1024 65535" $ sysctl -w net.ipv4.ip_local_port_range="1024 65535"
@ -112,7 +112,7 @@ theusername soft nofile 40000
Linux supports pluggable congestion control algorithms. Linux supports pluggable congestion control algorithms.
To get a list of congestion control algorithms that are available in your kernel run: To get a list of congestion control algorithms that are available in your kernel run:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl net.ipv4.tcp_available_congestion_control $ sysctl net.ipv4.tcp_available_congestion_control
@ -121,7 +121,7 @@ $ sysctl net.ipv4.tcp_available_congestion_control
If cubic and/or htcp are not listed, you need to research the control algorithms for your kernel. If cubic and/or htcp are not listed, you need to research the control algorithms for your kernel.
You can try setting the control to cubic with: You can try setting the control to cubic with:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ sysctl -w net.ipv4.tcp_congestion_control=cubic $ sysctl -w net.ipv4.tcp_congestion_control=cubic

2
jetty-documentation/src/main/asciidoc/administration/tuning/limit-load.adoc
View File

@ -24,7 +24,7 @@ To achieve optimal fair handling for all users of a server, it can be necessary
An instance of link:{JDURL}/org/eclipse/jetty/server/LowResourcesMonitor.html[LowResourcesMonitor] may be added to a Jetty Server to monitor for low resources situations and to take action to limit the number of idle connections on the server. An instance of link:{JDURL}/org/eclipse/jetty/server/LowResourcesMonitor.html[LowResourcesMonitor] may be added to a Jetty Server to monitor for low resources situations and to take action to limit the number of idle connections on the server.
To configure the low resources monitor, you can uncomment the jetty-lowresources.xml line from the start.ini configuration file, which has the effect of including the following XML configuration: To configure the low resources monitor, you can uncomment the jetty-lowresources.xml line from the start.ini configuration file, which has the effect of including the following XML configuration:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-server/src/main/config/etc/jetty-lowresources.xml[] include::{SRCDIR}/jetty-server/src/main/config/etc/jetty-lowresources.xml[]
---- ----

16
jetty-documentation/src/main/asciidoc/configuring/connectors/configuring-connectors.adoc
View File

@ -54,7 +54,7 @@ Most other settings are for expert configuration only.
The services a link:{JDURL}/org/eclipse/jetty/server/ServerConnector.html[`ServerConnector`] instance uses are set by constructor injection and once instantiated cannot be changed. The services a link:{JDURL}/org/eclipse/jetty/server/ServerConnector.html[`ServerConnector`] instance uses are set by constructor injection and once instantiated cannot be changed.
Most of the services may be defaulted with null or 0 values so that a reasonable default is used, thus for most purposes only the Server and the connection factories need to be passed to the connector constructor. In Jetty XML (that is, in link:{SRCDIR}/jetty-server/src/main/config/etc/jetty-http.xml[`jetty-http.xml`]), you can do this by: Most of the services may be defaulted with null or 0 values so that a reasonable default is used, thus for most purposes only the Server and the connection factories need to be passed to the connector constructor. In Jetty XML (that is, in link:{SRCDIR}/jetty-server/src/main/config/etc/jetty-http.xml[`jetty-http.xml`]), you can do this by:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.server.ServerConnector"> <New class="org.eclipse.jetty.server.ServerConnector">
<Arg name="server"><Ref refid="Server" /></Arg> <Arg name="server"><Ref refid="Server" /></Arg>
@ -76,7 +76,7 @@ Typically the defaults are sufficient for almost all deployments.
You configure connector network settings by calling setters on the connector before it is started. You configure connector network settings by calling setters on the connector before it is started.
For example, you can set the port with the Jetty XML: For example, you can set the port with the Jetty XML:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.server.ServerConnector"> <New class="org.eclipse.jetty.server.ServerConnector">
<Arg name="server"><Ref refid="Server" /></Arg> <Arg name="server"><Ref refid="Server" /></Arg>
@ -89,7 +89,7 @@ For example, you can set the port with the Jetty XML:
Values in Jetty XML can also be parameterized so that they may be passed from property files or set on the command line. Values in Jetty XML can also be parameterized so that they may be passed from property files or set on the command line.
Thus typically the port is set within Jetty XML, but uses the `Property` element to be customizable: Thus typically the port is set within Jetty XML, but uses the `Property` element to be customizable:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.server.ServerConnector"> <New class="org.eclipse.jetty.server.ServerConnector">
<Arg name="server"><Ref refid="Server" /></Arg> <Arg name="server"><Ref refid="Server" /></Arg>
@ -137,7 +137,7 @@ To avoid duplicate configuration, the standard Jetty distribution creates the co
A typical configuration of link:{JDURL}/org/eclipse/jetty/server/HttpConfiguration.html[HttpConfiguration] is: A typical configuration of link:{JDURL}/org/eclipse/jetty/server/HttpConfiguration.html[HttpConfiguration] is:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="httpConfig" class="org.eclipse.jetty.server.HttpConfiguration"> <New id="httpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
<Set name="secureScheme">https</Set> <Set name="secureScheme">https</Set>
@ -150,7 +150,7 @@ A typical configuration of link:{JDURL}/org/eclipse/jetty/server/HttpConfigurati
This example HttpConfiguration may be used by reference to the ID "`httpConfig`": This example HttpConfiguration may be used by reference to the ID "`httpConfig`":
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Call name="addConnector"> <Call name="addConnector">
<Arg> <Arg>
@ -173,7 +173,7 @@ This example HttpConfiguration may be used by reference to the ID "`httpConfig`"
For SSL based connectors (in `jetty-https.xml` and `jetty-http2.xml`), the common "`httpConfig`" instance is used as the basis to create an SSL specific configuration with ID "`sslHttpConfig`": For SSL based connectors (in `jetty-https.xml` and `jetty-http2.xml`), the common "`httpConfig`" instance is used as the basis to create an SSL specific configuration with ID "`sslHttpConfig`":
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="sslHttpConfig" class="org.eclipse.jetty.server.HttpConfiguration"> <New id="sslHttpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
<Arg><Ref refid="httpConfig"/></Arg> <Arg><Ref refid="httpConfig"/></Arg>
@ -212,7 +212,7 @@ ____
The `X-Forwarded-for` header and associated headers are a de facto standard where intermediaries add HTTP headers to each request they forward to describe the originating connection. The `X-Forwarded-for` header and associated headers are a de facto standard where intermediaries add HTTP headers to each request they forward to describe the originating connection.
These headers can be interpreted by an instance of link:{JDURL}/org/eclipse/jetty/server/ForwardedRequestCustomizer.html[`ForwardedRequestCustomizer`] which can be added to a `HttpConfiguration` as follows: These headers can be interpreted by an instance of link:{JDURL}/org/eclipse/jetty/server/ForwardedRequestCustomizer.html[`ForwardedRequestCustomizer`] which can be added to a `HttpConfiguration` as follows:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="httpConfig" class="org.eclipse.jetty.server.HttpConfiguration"> <New id="httpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
<Set name="outputBufferSize">32768</Set> <Set name="outputBufferSize">32768</Set>
@ -235,7 +235,7 @@ The connection factory can be added to any link:{JDURL}/org/eclipse/jetty/server
An example of adding the factory to a HTTP connector is: An example of adding the factory to a HTTP connector is:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Call name="addConnector"> <Call name="addConnector">
<Arg> <Arg>

40
jetty-documentation/src/main/asciidoc/configuring/connectors/configuring-ssl.adoc
View File

@ -90,7 +90,7 @@ You should read the full manuals of the tools you are using if you want to speci
The following command generates a key pair and certificate directly into file `keystore`: The following command generates a key pair and certificate directly into file `keystore`:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -keystore keystore -alias jetty -genkey -keyalg RSA $ keytool -keystore keystore -alias jetty -genkey -keyalg RSA
---- ----
@ -106,7 +106,7 @@ This command prompts for information about the certificate and for passwords to
The only mandatory response is to provide the fully qualified host name of the server at the "first and last name" prompt. The only mandatory response is to provide the fully qualified host name of the server at the "first and last name" prompt.
For example: For example:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -keystore keystore -alias jetty -genkey -keyalg RSA -sigalg SHA256withRSA $ keytool -keystore keystore -alias jetty -genkey -keyalg RSA -sigalg SHA256withRSA
Enter keystore password: password Enter keystore password: password
@ -139,7 +139,7 @@ If you want to use only a self signed certificate for some kind of internal admi
If you are using Java 8 or later, then you may also use the SAN extension to set one or more names that the certificate applies to: If you are using Java 8 or later, then you may also use the SAN extension to set one or more names that the certificate applies to:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -keystore keystore -alias jetty -genkey -keyalg RSA -sigalg SHA256withRSA -ext 'SAN=dns:jetty.eclipse.org,dns:*.jetty.org' $ keytool -keystore keystore -alias jetty -genkey -keyalg RSA -sigalg SHA256withRSA -ext 'SAN=dns:jetty.eclipse.org,dns:*.jetty.org'
... ...
@ -150,7 +150,7 @@ $ keytool -keystore keystore -alias jetty -genkey -keyalg RSA -sigalg SHA256with
The following command generates a key pair in the file `jetty.key`: The following command generates a key pair in the file `jetty.key`:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl genrsa -aes128 -out jetty.key $ openssl genrsa -aes128 -out jetty.key
---- ----
@ -159,7 +159,7 @@ You might also want to use the `-rand` file argument to provide an arbitrary fil
The following command generates a certificate for the key into the file `jetty.crt`: The following command generates a certificate for the key into the file `jetty.crt`:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl req -new -x509 -newkey rsa:2048 -sha256 -key jetty.key -out jetty.crt $ openssl req -new -x509 -newkey rsa:2048 -sha256 -key jetty.key -out jetty.crt
---- ----
@ -170,7 +170,7 @@ For the those with heightened security in mind, add -b4096 to get a 4069 bit key
The next command prompts for information about the certificate and for passwords to protect both the keystore and the keys within it. The next command prompts for information about the certificate and for passwords to protect both the keystore and the keys within it.
The only mandatory response is to provide the fully qualified host name of the server at the "Common Name" prompt. For example: The only mandatory response is to provide the fully qualified host name of the server at the "Common Name" prompt. For example:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl genrsa -aes128 -out jetty.key $ openssl genrsa -aes128 -out jetty.key
Generating RSA private key, 2048 bit long modulus Generating RSA private key, 2048 bit long modulus
@ -223,7 +223,7 @@ Each CA has its own instructions (look for JSSE or OpenSSL sections), but all in
The following command generates the file `jetty.csr` using `keytool` for a key/cert already in the keystore: The following command generates the file `jetty.csr` using `keytool` for a key/cert already in the keystore:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -certreq -alias jetty -keystore keystore -file jetty.csr $ keytool -certreq -alias jetty -keystore keystore -file jetty.csr
---- ----
@ -233,7 +233,7 @@ $ keytool -certreq -alias jetty -keystore keystore -file jetty.csr
The following command generates the file `jetty.csr` using OpenSSL for a key in the file `jetty.key`: The following command generates the file `jetty.csr` using OpenSSL for a key in the file `jetty.key`:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl req -new -key jetty.key -out jetty.csr $ openssl req -new -key jetty.key -out jetty.csr
---- ----
@ -281,14 +281,14 @@ Rcz6oCRvCGCe5kDB
The following command loads a PEM encoded certificate in the `jetty.crt` file into a JSSE keystore: The following command loads a PEM encoded certificate in the `jetty.crt` file into a JSSE keystore:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -keystore keystore -import -alias jetty -file jetty.crt -trustcacerts $ keytool -keystore keystore -import -alias jetty -file jetty.crt -trustcacerts
---- ----
If the certificate you receive from the CA is not in a format that `keytool` understands, you can use the `openssl` command to convert formats: If the certificate you receive from the CA is not in a format that `keytool` understands, you can use the `openssl` command to convert formats:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl x509 -in jetty.der -inform DER -outform PEM -out jetty.crt $ openssl x509 -in jetty.der -inform DER -outform PEM -out jetty.crt
---- ----
@ -301,14 +301,14 @@ The certificate can be one you generated yourself or one returned from a CA in r
The following OpenSSL command combines the keys in `jetty.key` and the certificate in the `jetty.crt` file into the `jetty.pkcs12` file: The following OpenSSL command combines the keys in `jetty.key` and the certificate in the `jetty.crt` file into the `jetty.pkcs12` file:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ openssl pkcs12 -inkey jetty.key -in jetty.crt -export -out jetty.pkcs12 $ openssl pkcs12 -inkey jetty.key -in jetty.crt -export -out jetty.pkcs12
---- ----
If you have a chain of certificates, because your CA is an intermediary, build the PKCS12 file as follows: If you have a chain of certificates, because your CA is an intermediary, build the PKCS12 file as follows:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ cat example.crt intermediate.crt [intermediate2.crt] ... rootCA.crt > cert-chain.txt $ cat example.crt intermediate.crt [intermediate2.crt] ... rootCA.crt > cert-chain.txt
$ openssl pkcs12 -export -inkey example.key -in cert-chain.txt -out example.pkcs12 $ openssl pkcs12 -export -inkey example.key -in cert-chain.txt -out example.pkcs12
@ -320,7 +320,7 @@ OpenSSL asks for an __export password__.
A non-empty password is required to make the next step work. A non-empty password is required to make the next step work.
Then load the resulting PKCS12 file into a JSSE keystore with `keytool`: Then load the resulting PKCS12 file into a JSSE keystore with `keytool`:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ keytool -importkeystore -srckeystore jetty.pkcs12 -srcstoretype PKCS12 -destkeystore keystore $ keytool -importkeystore -srckeystore jetty.pkcs12 -srcstoretype PKCS12 -destkeystore keystore
---- ----
@ -394,7 +394,7 @@ For those of you using the Jetty Distribution, the provided modules for https an
An example of this setup: An example of this setup:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
$ cd /path/to/mybase $ cd /path/to/mybase
$ java -jar /path/to/jetty-dist/start.jar --add-to-start=https $ java -jar /path/to/jetty-dist/start.jar --add-to-start=https
@ -454,7 +454,7 @@ If you have a need to adjust the Includes or Excludes, then this is best done wi
To do this, first create a new `${jetty.base}/etc/tweak-ssl.xml` (thiscan be any name, just avoid prefixing it with "jetty-"). To do this, first create a new `${jetty.base}/etc/tweak-ssl.xml` (thiscan be any name, just avoid prefixing it with "jetty-").
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN"
"http://www.eclipse.org/jetty/configure_9_3.dtd"> "http://www.eclipse.org/jetty/configure_9_3.dtd">
@ -478,7 +478,7 @@ You can do anything you want with the `SslContextFactory` in use by the Jetty Di
To make sure that your `${jetty.base}` uses this new XML, add it to the end of your `${jetty.base}/start.ini` To make sure that your `${jetty.base}` uses this new XML, add it to the end of your `${jetty.base}/start.ini`
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
$ cd /path/to/mybase $ cd /path/to/mybase
$ ls -l $ ls -l
@ -507,7 +507,7 @@ Some other Include / Exclude examples:
Example: Include all ciphers which support https://en.wikipedia.org/wiki/Forward_secrecy[Forward Secrecy] using regex: Example: Include all ciphers which support https://en.wikipedia.org/wiki/Forward_secrecy[Forward Secrecy] using regex:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Enable Forward Secrecy Ciphers. <!-- Enable Forward Secrecy Ciphers.
Note: this replaces the default Include Cipher list --> Note: this replaces the default Include Cipher list -->
@ -521,7 +521,7 @@ Example: Include all ciphers which support https://en.wikipedia.org/wiki/Forward
*Example*: Exclude all old, insecure or anonymous cipher suites: *Example*: Exclude all old, insecure or anonymous cipher suites:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Eliminate Old / Insecure / Anonymous Ciphers --> <!-- Eliminate Old / Insecure / Anonymous Ciphers -->
<Call name="addExcludeCipherSuites"> <Call name="addExcludeCipherSuites">
@ -539,7 +539,7 @@ Example: Include all ciphers which support https://en.wikipedia.org/wiki/Forward
*Example*: Since 2014 SSLv3 is considered insecure and should be disabled. *Example*: Since 2014 SSLv3 is considered insecure and should be disabled.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Eliminate Insecure Protocols --> <!-- Eliminate Insecure Protocols -->
<Call name="addExcludeProtocols"> <Call name="addExcludeProtocols">
@ -561,7 +561,7 @@ ____
*Example*: TLS renegotiation could be disabled too to prevent an attack based on this feature. *Example*: TLS renegotiation could be disabled too to prevent an attack based on this feature.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Set name="renegotiationAllowed">FALSE</Set> <Set name="renegotiationAllowed">FALSE</Set>
---- ----

12
jetty-documentation/src/main/asciidoc/configuring/connectors/setting-port80-access-for-non-root-user.adoc
View File

@ -25,7 +25,7 @@ This page presents several options to access port 80 as a non-root user, includi
On some Linux systems you can use the _ipchains REDIRECT_ mechanism to redirect from one port to another inside the kernel (if ipchains is not available, then usually iptables is): On some Linux systems you can use the _ipchains REDIRECT_ mechanism to redirect from one port to another inside the kernel (if ipchains is not available, then usually iptables is):
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
# /sbin/ipchains -I input --proto TCP --dport 80 -j REDIRECT 8080 # /sbin/ipchains -I input --proto TCP --dport 80 -j REDIRECT 8080
---- ----
@ -42,7 +42,7 @@ On many Linux systems you can use the iptables REDIRECT mechanism to redirect fr
You need to add something like the following to the startup scripts or your firewall rules: You need to add something like the following to the startup scripts or your firewall rules:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
# /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 # /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080
---- ----
@ -68,7 +68,7 @@ The `http.mod` is enabled by default in the distribution, while the link:#quicks
2. Ensure that you have link:#quickstart-changing-jetty-port[changed the http port] to 80 (and link:#quickstart-changing-https-port[changed the https port] to 443 if you are using SSL). 2. Ensure that you have link:#quickstart-changing-jetty-port[changed the http port] to 80 (and link:#quickstart-changing-https-port[changed the https port] to 443 if you are using SSL).
3. Enable the `setuid.mod` module: 3. Enable the `setuid.mod` module:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
# java -jar start.jar --add-to-start=setuid # java -jar start.jar --add-to-start=setuid
---- ----
@ -103,7 +103,7 @@ This code is hosted as part of the Jetty ToolChain project and it is released in
You can find the source code https://github.com/eclipsejetty.toolchain[here] in the https://github.com/eclipse/jetty.toolchain/jetty-setuid[jetty-setuid] project. You can find the source code https://github.com/eclipsejetty.toolchain[here] in the https://github.com/eclipse/jetty.toolchain/jetty-setuid[jetty-setuid] project.
Build it locally, which will produce a native library appropriate for the operating system: Build it locally, which will produce a native library appropriate for the operating system:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
# mvn clean install # mvn clean install
---- ----
@ -114,7 +114,7 @@ You might like to copy this file into your jetty distribution's lib directory.
6. Start jetty as the root user in your base directory, providing the location of the native library to java. 6. Start jetty as the root user in your base directory, providing the location of the native library to java.
Here's an example of how to do it on the command line, assuming were are in the link:#demo-webapps-base[demo-base] directory: Here's an example of how to do it on the command line, assuming were are in the link:#demo-webapps-base[demo-base] directory:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
# sudo java -Djava.library.path=libsetuid-linux -jar $JETTY_HOME/start.jar # sudo java -Djava.library.path=libsetuid-linux -jar $JETTY_HOME/start.jar
---- ----
@ -124,7 +124,7 @@ Here's an example of how to do it on the command line, assuming were are in the
Solaris 10 provides a User Rights Management framework that can permit users and processes superuser-like abilities: Solaris 10 provides a User Rights Management framework that can permit users and processes superuser-like abilities:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
usermod -K defaultpriv=basic,net_privaddr myself usermod -K defaultpriv=basic,net_privaddr myself
---- ----

10
jetty-documentation/src/main/asciidoc/configuring/contexts/configuring-virtual-hosts.adoc
View File

@ -60,7 +60,7 @@ You supply a list of IP addresses and names at which the web application is reac
Suppose you have a webapp called `blah.war`, that you want all of the above names and addresses to be served at path "`/blah`". Suppose you have a webapp called `blah.war`, that you want all of the above names and addresses to be served at path "`/blah`".
Here's how you would configure the virtual hosts with a link:#deployable-descriptor-file[context XML] file: Here's how you would configure the virtual hosts with a link:#deployable-descriptor-file[context XML] file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -100,7 +100,7 @@ Using the method of preparing link:#deployable-descriptor-files[contextXML] file
For `blah` webapp: For `blah` webapp:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -126,7 +126,7 @@ These URLs now resolve to the blah context (ie `blah.war`):
For `other` webapp: For `other` webapp:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -175,7 +175,7 @@ To achieve this, we simply use the same context path of `/` for each of our weba
For foo webapp: For foo webapp:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -195,7 +195,7 @@ For foo webapp:
For bar webapp: For bar webapp:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

12
jetty-documentation/src/main/asciidoc/configuring/contexts/custom-error-pages.adoc
View File

@ -30,7 +30,7 @@ This element creates a mapping between the error-code or exception-type to the l
Error code example: Error code example:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<error-page> <error-page>
<error-code>404</error-code> <error-code>404</error-code>
@ -41,7 +41,7 @@ Error code example:
Exception example: Exception example:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<error-page> <error-page>
<exception-type>java.io.IOException</exception-type> <exception-type>java.io.IOException</exception-type>
@ -72,7 +72,7 @@ javax.servlet.error.status_code::
You can use context IoC XML files to configure the default error page mappings with more flexibility than is available with `web.xml`, specifically with the support of error code ranges. You can use context IoC XML files to configure the default error page mappings with more flexibility than is available with `web.xml`, specifically with the support of error code ranges.
Context files are normally located in `${jetty.home}/webapps/` (see `DeployerManager` for more details) and an example of more flexible error page mapping is below: Context files are normally located in `${jetty.home}/webapps/` (see `DeployerManager` for more details) and an example of more flexible error page mapping is below:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.eclipse.org/configure.dtd"> <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.eclipse.org/configure.dtd">
@ -120,7 +120,7 @@ Context files are normally located in `${jetty.home}/webapps/` (see `DeployerMan
If no error page mapping is defined, or if the error page resource itself has an error, then the error page will be generated by an instance of `ErrorHandler` configured either the Context or the Server. If no error page mapping is defined, or if the error page resource itself has an error, then the error page will be generated by an instance of `ErrorHandler` configured either the Context or the Server.
An `ErrorHandler` may extend the `ErrorHandler` class and may totally replace the handle method to generate an error page, or it can implement some or all of the following methods to partially modify the error pages: An `ErrorHandler` may extend the `ErrorHandler` class and may totally replace the handle method to generate an error page, or it can implement some or all of the following methods to partially modify the error pages:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) throws IOException void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) throws IOException
void handleErrorPage(HttpServletRequest request, Writer writer, int code, String message) throws IOException void handleErrorPage(HttpServletRequest request, Writer writer, int code, String message) throws IOException
@ -134,7 +134,7 @@ void writeErrorPageStacks(HttpServletRequest request, Writer writer) throws IOEx
An `ErrorHandler` instance may be set on a Context by calling the `ContextHandler.setErrorHandler` method. This can be done by embedded code or via context IoC XML. An `ErrorHandler` instance may be set on a Context by calling the `ContextHandler.setErrorHandler` method. This can be done by embedded code or via context IoC XML.
For example: For example:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.server.handler.ContextHandler"> <Configure class="org.eclipse.jetty.server.handler.ContextHandler">
... ...
@ -148,7 +148,7 @@ For example:
An `ErrorHandler` instance may be set on the entire server by setting it as a dependent bean on the Server instance. An `ErrorHandler` instance may be set on the entire server by setting it as a dependent bean on the Server instance.
This can be done by calling `Server.addBean(Object)` via embedded code or in `jetty.xml` IoC XML like: This can be done by calling `Server.addBean(Object)` via embedded code or in `jetty.xml` IoC XML like:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.server.Server"> <Configure id="Server" class="org.eclipse.jetty.server.Server">
... ...

4
jetty-documentation/src/main/asciidoc/configuring/contexts/serving-webapp-from-particular-port.adoc
View File

@ -41,14 +41,14 @@ When creating new configurations for alternative server:
The following example creates another server instance and configures it with a connector and deployer: The following example creates another server instance and configures it with a connector and deployer:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/resources/jetty-otherserver.xml[] include::{SRCDIR}/examples/embedded/src/main/resources/jetty-otherserver.xml[]
---- ----
To run the other server, add the extra configuration file(s) to the command line: To run the other server, add the extra configuration file(s) to the command line:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
java -jar start.jar jetty-otherserver.xml java -jar start.jar jetty-otherserver.xml
---- ----

2
jetty-documentation/src/main/asciidoc/configuring/contexts/setting-context-path.adoc
View File

@ -43,7 +43,7 @@ If a web application is deployed using the WebAppProvider of the DeploymentManag
If a web application is deployed using the `WebAppProvider` of the `DeploymentManager` with an XML IoC file to configure the context, then the `setContextPath` method can be called within that file. If a web application is deployed using the `WebAppProvider` of the `DeploymentManager` with an XML IoC file to configure the context, then the `setContextPath` method can be called within that file.
For example: For example:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
<Set name="contextPath">/test</Set> <Set name="contextPath">/test</Set>

4
jetty-documentation/src/main/asciidoc/configuring/contexts/setting-form-size.adoc
View File

@ -30,7 +30,7 @@ This can be done either in a context XML deployment descriptor external to the w
In either case the syntax of the XML file is the same: In either case the syntax of the XML file is the same:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
@ -44,7 +44,7 @@ In either case the syntax of the XML file is the same:
Set an attribute on the Server instance for which you want to modify the maximum form content size: Set an attribute on the Server instance for which you want to modify the maximum form content size:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.server.Server"> <Configure class="org.eclipse.jetty.server.Server">
<Call name="setAttribute"> <Call name="setAttribute">

12
jetty-documentation/src/main/asciidoc/configuring/contexts/temporary-directories.adoc
View File

@ -49,7 +49,7 @@ As usual with Jetty, you can either set this attribute in a context xml file, or
Here's an example of setting it in an xml file: Here's an example of setting it in an xml file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -65,7 +65,7 @@ Here's an example of setting it in an xml file:
The equivalent in code is: The equivalent in code is:
[source,java] [source, java, subs="{sub-order}"]
---- ----
WebAppContext context = new WebAppContext(); WebAppContext context = new WebAppContext();
context.setContextPath("/test"); context.setContextPath("/test");
@ -80,7 +80,7 @@ There are several ways to use a particular directory as the temporary directory:
call WebAppContext.setTempDirectory(String dir):: call WebAppContext.setTempDirectory(String dir)::
Like before this can be accomplished with an xml file or directly in code. Here's an example of setting the temp directory in xml: Like before this can be accomplished with an xml file or directly in code. Here's an example of setting the temp directory in xml:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -93,7 +93,7 @@ call WebAppContext.setTempDirectory(String dir)::
Here's an example of doing it with java code: Here's an example of doing it with java code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
WebAppContext context = new WebAppContext(); WebAppContext context = new WebAppContext();
context.setContextPath("/test"); context.setContextPath("/test");
@ -104,7 +104,7 @@ context.setTempDirectory(new File("/some/dir/foo"));
set the `javax.servlet.context.tempdir` context attribute:: set the `javax.servlet.context.tempdir` context attribute::
You should set this context attribute with the name of directory you want to use as the temp directory. Again, you can do this in xml: You should set this context attribute with the name of directory you want to use as the temp directory. Again, you can do this in xml:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -121,7 +121,7 @@ set the `javax.servlet.context.tempdir` context attribute::
Or in java: Or in java:
[source,java] [source, java, subs="{sub-order}"]
---- ----
WebAppContext context = new WebAppContext(); WebAppContext context = new WebAppContext();
context.setContextPath("/test"); context.setContextPath("/test");

12
jetty-documentation/src/main/asciidoc/configuring/deploying/configuring-specific-webapp-deployment.adoc
View File

@ -41,7 +41,7 @@ contextPath::
For example, here is a descriptor file that deploys the file `/opt/myapp/myapp.war` to the context path `/wiki`: For example, here is a descriptor file that deploys the file `/opt/myapp/myapp.war` to the context path `/wiki`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -58,7 +58,7 @@ Both `SystemProperty` and `Property` elements can be used in the descriptor file
For example, if the system property is set tp `myapp.home=/opt/myapp`, the previous example can be rewritten as: For example, if the system property is set tp `myapp.home=/opt/myapp`, the previous example can be rewritten as:
____ ____
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -81,7 +81,7 @@ Here are some examples that configure advanced options in the descriptor file.
This first example tells Jetty not to expand the WAR file when deploying it. This first example tells Jetty not to expand the WAR file when deploying it.
This can help make it clear that users should not make changes to the temporary unpacked WAR because such changes do not persist, and therefore do not apply the next time the web application deploys. This can help make it clear that users should not make changes to the temporary unpacked WAR because such changes do not persist, and therefore do not apply the next time the web application deploys.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -97,7 +97,7 @@ The next example retrieves the JavaEE Servlet context and sets an initialization
The `setAttribute` method can also be used to set a Servlet context attribute. The `setAttribute` method can also be used to set a Servlet context attribute.
However, since the `web.xml` for the web application is processed after the deployment descriptor, the `web.xml` values overwrite identically named attributes from the deployment descriptor. However, since the `web.xml` for the web application is processed after the deployment descriptor, the `web.xml` values overwrite identically named attributes from the deployment descriptor.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -118,7 +118,7 @@ The following example sets a special `web.xml` override descriptor.
This descriptor is processed after the web application's `web.xml`, so it may override identically named attributes. This descriptor is processed after the web application's `web.xml`, so it may override identically named attributes.
This feature is useful when adding parameters or additional Servlet mappings without breaking open a packed WAR file. This feature is useful when adding parameters or additional Servlet mappings without breaking open a packed WAR file.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -133,7 +133,7 @@ This feature is useful when adding parameters or additional Servlet mappings wit
The next example configures not only the web application context, but also a database connection pool (see xref:jndi-datasource-examples[] that the application can then use. The next example configures not only the web application context, but also a database connection pool (see xref:jndi-datasource-examples[] that the application can then use.
If the `web.xml` does not include a reference to this data source, an override descriptor mechanism (as shown in the previous example) can be used to include it. If the `web.xml` does not include a reference to this data source, an override descriptor mechanism (as shown in the previous example) can be used to include it.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

2
jetty-documentation/src/main/asciidoc/configuring/deploying/deployment-architecture.adoc
View File

@ -79,7 +79,7 @@ It supports hot (re)deployment.
The basic operation of the `WebAppProvider` is to periodically scan a directory for deployables. The basic operation of the `WebAppProvider` is to periodically scan a directory for deployables.
In the standard Jetty Distribution, this is configured in the `${jetty.home}/etc/jetty-deploy.xml` file. In the standard Jetty Distribution, this is configured in the `${jetty.home}/etc/jetty-deploy.xml` file.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

10
jetty-documentation/src/main/asciidoc/configuring/deploying/deployment-processing-webapps.adoc
View File

@ -130,7 +130,7 @@ If you have only one webapp that you wish to affect, this may be the easiest opt
You will, however, either need to have a context xml file that represents your web app, or you need to call the equivalent in code. You will, however, either need to have a context xml file that represents your web app, or you need to call the equivalent in code.
Let's see an example of how we would add in the Configurations for both JNDI _and_ annotations: Let's see an example of how we would add in the Configurations for both JNDI _and_ annotations:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -162,7 +162,7 @@ Of course, you can also use this method to reduce the Configurations applied to
If you use the link:#deployment-architecture[deployer], you can set up the list of Configuration classes on the link:#default-web-app-provider[WebAppProvider]. If you use the link:#deployment-architecture[deployer], you can set up the list of Configuration classes on the link:#default-web-app-provider[WebAppProvider].
They will then be applied to each `WebAppContext` deployed by the deployer: They will then be applied to each `WebAppContext` deployed by the deployer:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -206,7 +206,7 @@ Instead of having to enumerate the list in its entirety, you can simply nominate
Let's look at an example of using this method to add in Configuration support for JNDI - as usual you can either do this in an xml file, or via equivalent code. Let's look at an example of using this method to add in Configuration support for JNDI - as usual you can either do this in an xml file, or via equivalent code.
This example uses an xml file, in fact it is the `$JETTY_HOME/etc/jetty-plus.xml` file from the Jetty distribution: This example uses an xml file, in fact it is the `$JETTY_HOME/etc/jetty-plus.xml` file from the Jetty distribution:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -256,7 +256,7 @@ The value of this attribute is a regexp that defines which _jars_ and _class dir
Here's an example from a context xml file (although as always, you could have accomplished the same in code), which would match any jar whose name starts with "foo-" or "bar-", or a directory named "classes": Here's an example from a context xml file (although as always, you could have accomplished the same in code), which would match any jar whose name starts with "foo-" or "bar-", or a directory named "classes":
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -282,7 +282,7 @@ This can be particularly useful when you have dozens of jars in `WEB-INF/lib`, b
Here's an example in a xml file of a pattern that matches any jar that starts with `spring-`: Here's an example in a xml file of a pattern that matches any jar that starts with `spring-`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

2
jetty-documentation/src/main/asciidoc/configuring/deploying/hot-deployment.adoc
View File

@ -32,7 +32,7 @@ scanInterval::
The default location for this configuration is in the `${jetty.home}/etc/jetty-deploy.xml` file. The default location for this configuration is in the `${jetty.home}/etc/jetty-deploy.xml` file.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

28
jetty-documentation/src/main/asciidoc/configuring/deploying/overlay-deployer.adoc
View File

@ -61,7 +61,7 @@ The JTrac issue tracking web application is a good example of a typical web appl
The files for this demonstration are available in overlays-demo.tar.gz. The files for this demonstration are available in overlays-demo.tar.gz.
The demonstation can be expanded on top of the jetty distribution; this tutorial expands it to /tmp and installs the components step-by-step: The demonstation can be expanded on top of the jetty distribution; this tutorial expands it to /tmp and installs the components step-by-step:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ cd /tmp $ cd /tmp
$ wget http://webtide.intalio.com/wp-content/uploads/2011/05/overlays-demo.tar.gz $ wget http://webtide.intalio.com/wp-content/uploads/2011/05/overlays-demo.tar.gz
@ -76,7 +76,7 @@ Overlays support is included in jetty distributions from 7.4.1-SNAPSHOT onwards,
The `start.ini` file needs edited so that it includes the overlay option and configuration file. The `start.ini` file needs edited so that it includes the overlay option and configuration file.
The resulting file should look like: The resulting file should look like:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
OPTIONS=Server,jsp,jmx,resources,websocket,ext,overlay OPTIONS=Server,jsp,jmx,resources,websocket,ext,overlay
etc/jetty.xml etc/jetty.xml
@ -87,7 +87,7 @@ etc/jetty-overlay.xml
The mechanics of this are in etc/jetty-deploy.xml, which installs the `OverlayedAppProvider` into the `DeploymentManager`. The mechanics of this are in etc/jetty-deploy.xml, which installs the `OverlayedAppProvider` into the `DeploymentManager`.
Jetty can then be started normally: Jetty can then be started normally:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ java -jar start.jar $ java -jar start.jar
---- ----
@ -104,7 +104,7 @@ ____
The WAR file for this demo can be downloaded and deployed the using the following commands, which downloads and extracts the WAR file to the $JETTY_HOME/overlays/webapps directory. The WAR file for this demo can be downloaded and deployed the using the following commands, which downloads and extracts the WAR file to the $JETTY_HOME/overlays/webapps directory.
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ cd /tmp $ cd /tmp
$ wget -O jtrac.zip http://sourceforge.net/projects/j-trac/files/jtrac/2.1.0/jtrac-2.1.0.zip/download $ wget -O jtrac.zip http://sourceforge.net/projects/j-trac/files/jtrac/2.1.0/jtrac-2.1.0.zip/download
@ -114,7 +114,7 @@ $ mv jtrac/jtrac.war $JETTY_HOME/overlays/webapps
When these commands (or equivalent) have been executed, a message that the `OverlayedAppProvider` has extracted and loaded the WAR file will be displayed in the Jetty server window: When these commands (or equivalent) have been executed, a message that the `OverlayedAppProvider` has extracted and loaded the WAR file will be displayed in the Jetty server window:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
2011-05-06 10:31:54.678:INFO:OverlayedAppProvider:Extract jar:file:/tmp/jetty-distribution-7.4.1-SNAPSHOT/overlays/webapps/jtrac-2.1.0.war!/ to /tmp/jtrac-2.1.0_236811420856825222.extract 2011-05-06 10:31:54.678:INFO:OverlayedAppProvider:Extract jar:file:/tmp/jetty-distribution-7.4.1-SNAPSHOT/overlays/webapps/jtrac-2.1.0.war!/ to /tmp/jtrac-2.1.0_236811420856825222.extract
2011-05-06 10:31:55.235:INFO:OverlayedAppProvider:loaded jtrac-2.1.0@1304641914666 2011-05-06 10:31:55.235:INFO:OverlayedAppProvider:loaded jtrac-2.1.0@1304641914666
@ -128,21 +128,21 @@ A template overlay is a WAR structured directory/archive that contains the files
The demo template can be installed from the downloaded files with the command: The demo template can be installed from the downloaded files with the command:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ mv $OVERLAYS/jtracTemplate\=jtrac-2.1.0 $JETTY_HOME/overlays/templates/ $ mv $OVERLAYS/jtracTemplate\=jtrac-2.1.0 $JETTY_HOME/overlays/templates/
---- ----
In the Jetty server window, a message similar to this will be displayed confirmed that the template is loaded: In the Jetty server window, a message similar to this will be displayed confirmed that the template is loaded:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
2011-05-06 11:00:08.716:INFO:OverlayedAppProvider:loaded jtracTemplate=jtrac-2.1.0@1304643608715 2011-05-06 11:00:08.716:INFO:OverlayedAppProvider:loaded jtracTemplate=jtrac-2.1.0@1304643608715
---- ----
The contents of the loaded template are as follows: The contents of the loaded template are as follows:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
templates/jtracTemplate=jtrac-2.1.0 templates/jtracTemplate=jtrac-2.1.0
|__ WEB-INF |__ WEB-INF
@ -165,7 +165,7 @@ WEB-INF/overlay.xml::
A Jetty XML formatted IoC file that injects/configures the `ContextHandler` for each instance. \ A Jetty XML formatted IoC file that injects/configures the `ContextHandler` for each instance. \
In this case it sets up the context path: In this case it sets up the context path:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
@ -178,7 +178,7 @@ WEB-INF/template.xml::
A Jetty XML formatted IoC file that injects/configures the resource cache and classloader that all instances of the template share. A Jetty XML formatted IoC file that injects/configures the resource cache and classloader that all instances of the template share.
It runs only once per load of the template: It runs only once per load of the template:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
@ -197,7 +197,7 @@ WEB-INF/web-overlay.xml::
servlets. servlets.
In this example it sets the application home and springs `webAppRootKey`: In this example it sets the application home and springs `webAppRootKey`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
@ -225,7 +225,7 @@ The Overlay Deployer allows all these changes to be made in one structure; moreo
Now that the template is installed, one or more instance overlays can be implemented to deploy the actual web applications: Now that the template is installed, one or more instance overlays can be implemented to deploy the actual web applications:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ mv /tmp/overlays/instances/jtracTemplate\=blue $JETTY_HOME/overlays/instances/ $ mv /tmp/overlays/instances/jtracTemplate\=blue $JETTY_HOME/overlays/instances/
$ mv /tmp/overlays/instances/jtracTemplate\=red $JETTY_HOME/overlays/instances/ $ mv /tmp/overlays/instances/jtracTemplate\=red $JETTY_HOME/overlays/instances/
@ -235,7 +235,7 @@ $ mv /tmp/overlays/instances/jtracTemplate\=blue $JETTY_HOME/overlays/instances/
As each instance moves into place, the Jetty server window reacts and deploys the instance. As each instance moves into place, the Jetty server window reacts and deploys the instance.
Within each instance, there is the structure: Within each instance, there is the structure:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
instances/jtracTemplate=red/ instances/jtracTemplate=red/
|__ WEB-INF |__ WEB-INF
@ -249,7 +249,7 @@ WEB-INF/overlay.xml::
A Jetty XML format IoC file that injects/configures the context for the instance. A Jetty XML format IoC file that injects/configures the context for the instance.
In this case it sets up a virtual host for the instance: In this case it sets up a virtual host for the instance:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">

12
jetty-documentation/src/main/asciidoc/configuring/deploying/quickstart-webapp.adoc
View File

@ -38,7 +38,7 @@ To use quickstart the module has to be available to the Jetty instance.
In a maven project this is done by adding a dependency on the artifact ID `jetty-quickstart`. In a maven project this is done by adding a dependency on the artifact ID `jetty-quickstart`.
In a standard Jetty distribution it can be configured with the following command: In a standard Jetty distribution it can be configured with the following command:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ java -jar $JETTY_HOME/start.jar --add-to-startd=quickstart $ java -jar $JETTY_HOME/start.jar --add-to-startd=quickstart
---- ----
@ -47,7 +47,7 @@ Deployed webapps need to be instances of link:{JDURL}/org/eclipse/jetty/quicksta
If a web application already has a `webapps/myapp.xml` file, simply change the class in the Configure element. If a web application already has a `webapps/myapp.xml` file, simply change the class in the Configure element.
Otherwise, create a `webapps/myapp.xml` file as follows: Otherwise, create a `webapps/myapp.xml` file as follows:
[source, xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
@ -65,9 +65,9 @@ On subsequent deployments, all the discovery steps are skipped and the `quicksta
It is also possible to preconfigure a war file manually by running the class link:{JDURL}/org/eclipse/jetty/quickstart/PreconfigureQuickStartWar.html[org.eclipse.jetty.quickstart.PreconfigureQuickStartWar] with the jetty-all-uber (aggregate) jar: It is also possible to preconfigure a war file manually by running the class link:{JDURL}/org/eclipse/jetty/quickstart/PreconfigureQuickStartWar.html[org.eclipse.jetty.quickstart.PreconfigureQuickStartWar] with the jetty-all-uber (aggregate) jar:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ java -cp jetty-all-@project.version@-uber.jar org.eclipse.jetty.quickstart.PreconfigureQuickStartWar myapp.war $ java -cp jetty-all-{VERSION}-uber.jar org.eclipse.jetty.quickstart.PreconfigureQuickStartWar myapp.war
---- ----
This will create the `quickstart-web.xml` file before the first deployment. This will create the `quickstart-web.xml` file before the first deployment.
@ -80,7 +80,7 @@ Of course precompiling JSPs is an excellent way to improve the start time of a w
Since jetty 9.2.0, the Apache Jasper JSP implementation has been used and has been augmented to allow the TLD scan to be skipped. Since jetty 9.2.0, the Apache Jasper JSP implementation has been used and has been augmented to allow the TLD scan to be skipped.
This can be done by adding a `context-param` to the `web.xml` file (this is done automatically by the Jetty Maven JSPC plugin): This can be done by adding a `context-param` to the `web.xml` file (this is done automatically by the Jetty Maven JSPC plugin):
[source, xml] [source, xml, subs="{sub-order}"]
---- ----
<context-param> <context-param>
<param-name>org.eclipse.jetty.jsp.precompiled</param-name> <param-name>org.eclipse.jetty.jsp.precompiled</param-name>
@ -94,7 +94,7 @@ The Jetty `start.jar` mechanism is a very powerful and flexible mechanism for co
However, this mechanism does take some time to build the `classpath`. However, this mechanism does take some time to build the `classpath`.
The start.jar mechanism can be bypassed by using the `–dry-run` option to generate and reuse a complete command line to start Jetty at a later time: The start.jar mechanism can be bypassed by using the `–dry-run` option to generate and reuse a complete command line to start Jetty at a later time:
[source, screen] [source, screen, subs="{sub-order}"]
---- ----
$ RUN=$(java -jar $JETTY_HOME/start.jar --dry-run) $ RUN=$(java -jar $JETTY_HOME/start.jar --dry-run)
$ eval $RUN $ eval $RUN

2
jetty-documentation/src/main/asciidoc/configuring/deploying/setting-deployment-bindings.adoc
View File

@ -28,7 +28,7 @@ There are a handful of bindings that exist within the core distribution of Jetty
* `DebugBinding` (any specified)–Attaches a binding and prints logging information of a context going through the specified binding target. * `DebugBinding` (any specified)–Attaches a binding and prints logging information of a context going through the specified binding target.
* `GlobalWebappConfigBinding` (deploying)–Allows the user to override various settings of a webapp's context globally for all contexts. * `GlobalWebappConfigBinding` (deploying)–Allows the user to override various settings of a webapp's context globally for all contexts.
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Call name="addLifeCycleBinding"> <Call name="addLifeCycleBinding">
<Arg> <Arg>

2
jetty-documentation/src/main/asciidoc/configuring/deploying/static-content-deployment.adoc
View File

@ -20,7 +20,7 @@
To serve purely static content, the Jetty Deployment Descriptor XML concepts and the internal `ResourceHandler` can be used. To serve purely static content, the Jetty Deployment Descriptor XML concepts and the internal `ResourceHandler` can be used.
Create a file called `scratch.xml` in the `${jetty.home}/webapps` directory and paste the following file contents in it. Create a file called `scratch.xml` in the `${jetty.home}/webapps` directory and paste the following file contents in it.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>

22
jetty-documentation/src/main/asciidoc/configuring/jsp/configuring-jsp.adoc
View File

@ -35,7 +35,7 @@ link:#startup-modules[module] is set to Apache Jasper. To change to use
Glassfish Jasper instead, edit the `$JETTY_HOME/start.d/jsp.mod` file Glassfish Jasper instead, edit the `$JETTY_HOME/start.d/jsp.mod` file
and change the line indicated: and change the line indicated:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-distribution/src/main/resources/modules/jsp.mod[] include::{SRCDIR}/jetty-distribution/src/main/resources/modules/jsp.mod[]
---- ----
@ -85,7 +85,7 @@ For example, suppose you have precompiled your jsps with the custom
package prefix of `com.acme`, then you would add the following lines to package prefix of `com.acme`, then you would add the following lines to
your web.xml file: your web.xml file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<context-param> <context-param>
<param-name>org.eclipse.jetty.servlet.jspPackagePrefix</param-name> <param-name>org.eclipse.jetty.servlet.jspPackagePrefix</param-name>
@ -332,7 +332,7 @@ recompilation. Here is a factoring out of the various options:
* Check the JSP files for possible recompilation on every request: * Check the JSP files for possible recompilation on every request:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<init-param> <init-param>
@ -345,7 +345,7 @@ recompilation. Here is a factoring out of the various options:
* Only check approximately every N seconds, where a request triggers the * Only check approximately every N seconds, where a request triggers the
time-lapse calculation. This example checks every 60 seconds: time-lapse calculation. This example checks every 60 seconds:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<init-param> <init-param>
@ -363,7 +363,7 @@ time-lapse calculation. This example checks every 60 seconds:
hit. (Be aware that this ''reload-interval'' parameter is shorthand for hit. (Be aware that this ''reload-interval'' parameter is shorthand for
a ''development=false'' and ''checkInterval=0'' combination.): a ''development=false'' and ''checkInterval=0'' combination.):
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<init-param> <init-param>
@ -377,7 +377,7 @@ a ''development=false'' and ''checkInterval=0'' combination.):
thread to do checks every N seconds. This example checks every 60 thread to do checks every N seconds. This example checks every 60
seconds: seconds:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<init-param> <init-param>
@ -407,7 +407,7 @@ Jetty, apply your changes, and use it instead of the shipped version.
The example below shows how to do this when using the Jetty Maven The example below shows how to do this when using the Jetty Maven
plugin. plugin.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<plugin> <plugin>
@ -427,7 +427,7 @@ settings for just one or a few of your webapps, copy the
a link:#intro-jetty-configuration-contexts[context xml] file to set this a link:#intro-jetty-configuration-contexts[context xml] file to set this
file as the defaultsDescriptor for your webapp. Here's a snippet: file as the defaultsDescriptor for your webapp. Here's a snippet:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class=>"org.eclipse.jetty.webapp.WebAppContext"> <Configure class=>"org.eclipse.jetty.webapp.WebAppContext">
@ -453,7 +453,7 @@ may also add (but not remove) servlet-mappings. You can use the entry in
link:#webdefault-xml[$JETTY_HOME/etc/webdefault.xml] as a starting link:#webdefault-xml[$JETTY_HOME/etc/webdefault.xml] as a starting
point. point.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<servlet id="jsp"> <servlet id="jsp">
@ -547,7 +547,7 @@ link:#embedded-examples[Embedded Examples] section includes a
link:#embedded-webapp-jsp[worked code example] of how to do this, here's link:#embedded-webapp-jsp[worked code example] of how to do this, here's
a snippet from it: a snippet from it:
[source,java] [source, java, subs="{sub-order}"]
---- ----
webapp.setAttribute("org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern",".*/[^/]*taglibs.*\\.jar$"); webapp.setAttribute("org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern",".*/[^/]*taglibs.*\\.jar$");
---- ----
@ -575,7 +575,7 @@ $JETTY_HOME/lib/ext.
You should make your JSF jars dependencies of the plugin and _not_ the You should make your JSF jars dependencies of the plugin and _not_ the
webapp itself. For example: webapp itself. For example:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<plugin> <plugin>

18
jetty-documentation/src/main/asciidoc/configuring/security/authentication.adoc
View File

@ -53,7 +53,7 @@ Below is an example taken from the
link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/webapp/WEB-INF/web.xml?h=release-9[jetty-test-webapp link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/webapp/WEB-INF/web.xml?h=release-9[jetty-test-webapp
web.xml] that configures BASIC authentication: web.xml] that configures BASIC authentication:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<login-config> <login-config>
<auth-method>BASIC</auth-method> <auth-method>BASIC</auth-method>
@ -67,7 +67,7 @@ link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/webapp/WEB-INF
web.xml] also includes commented out examples of other DIGEST and FORM web.xml] also includes commented out examples of other DIGEST and FORM
configuration: configuration:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<login-config> <login-config>
<auth-method>FORM</auth-method> <auth-method>FORM</auth-method>
@ -86,7 +86,7 @@ from the
link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/webapp/logon.html?h=release-9[test link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/webapp/logon.html?h=release-9[test
webapp logon.html]: webapp logon.html]:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<HTML> <HTML>
<H1>FORM Authentication demo</H1> <H1>FORM Authentication demo</H1>
@ -181,7 +181,7 @@ example of an xml file that defines an in-memory type of LoginService
called the called the
link:{JDURL}/org/eclipse/jetty/security/HashLoginService.html[HashLoginService]: link:{JDURL}/org/eclipse/jetty/security/HashLoginService.html[HashLoginService]:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.server.Server"> <Configure id="Server" class="org.eclipse.jetty.server.Server">
@ -205,7 +205,7 @@ telling the context the name of the LoginService, or passing it the
LoginService instance. Here's an example of doing both of these, using a LoginService instance. Here's an example of doing both of these, using a
link:#deployable-descriptor-file[context xml file]: link:#deployable-descriptor-file[context xml file]:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -231,7 +231,7 @@ Alternatively, you can define a LoginService for just a single web
application. Here's how to define the same HashLoginService, but inside application. Here's how to define the same HashLoginService, but inside
a link:#deployable-descriptor-file[context xml file]: a link:#deployable-descriptor-file[context xml file]:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -331,7 +331,7 @@ guest: guest,read-only
You configure the HashLoginService with a name and a reference to the You configure the HashLoginService with a name and a reference to the
location of the properties file: location of the properties file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Item> <Item>
@ -348,7 +348,7 @@ You can also configure it to check the properties file regularly for
changes and reload when changes are detected. The reloadInterval is in changes and reload when changes are detected. The reloadInterval is in
seconds: seconds:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.security.HashLoginService"> <New class="org.eclipse.jetty.security.HashLoginService">
@ -450,7 +450,7 @@ prefix.
You define a JDBCLoginService with the name of the realm and the You define a JDBCLoginService with the name of the realm and the
location of the properties file describing the database: location of the properties file describing the database:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.security.JDBCLoginService"> <New class="org.eclipse.jetty.security.JDBCLoginService">

6
jetty-documentation/src/main/asciidoc/configuring/security/configuring-form-size.adoc
View File

@ -34,7 +34,7 @@ To configure the form limits for a sinlge webapplication, the context
handler (or webappContext) instance must be configured using the handler (or webappContext) instance must be configured using the
following methods: following methods:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContextHandler.setMaxFormContentSize(int maxSizeInBytes); ContextHandler.setMaxFormContentSize(int maxSizeInBytes);
ContextHandler.setMaxFormKeys(int formKeys); ContextHandler.setMaxFormKeys(int formKeys);
@ -45,7 +45,7 @@ These methods may be called directly when embedding jetty, but more
commonly are configured from a context XML file or WEB-INF/jetty-web.xml commonly are configured from a context XML file or WEB-INF/jetty-web.xml
file: file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -64,7 +64,7 @@ server attributes are inspected to see if a server wide limit has been
set on the size or keys. The following XML shows how these attributes set on the size or keys. The following XML shows how these attributes
can be set in jetty.xml: can be set in jetty.xml:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<configure class="org.eclipse.jetty.server.Server"> <configure class="org.eclipse.jetty.server.Server">

12
jetty-documentation/src/main/asciidoc/configuring/security/jaas-support.adoc
View File

@ -71,7 +71,7 @@ Configure a jetty `org.eclipse.jetty.jaas.JAASLoginService` to match the
<realm-name> in your web.xml file. For example, if the `web.xml` <realm-name> in your web.xml file. For example, if the `web.xml`
contains a realm called "xyz" like so: contains a realm called "xyz" like so:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<login-config> <login-config>
<auth-method>FORM</auth-method> <auth-method>FORM</auth-method>
@ -86,7 +86,7 @@ contains a realm called "xyz" like so:
Then you need to create a JAASLoginService with the matching name of Then you need to create a JAASLoginService with the matching name of
"xyz": "xyz":
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.jaas.JAASLoginService"> <New class="org.eclipse.jetty.jaas.JAASLoginService">
<Set name="Name">Test JAAS Realm</Set> <Set name="Name">Test JAAS Realm</Set>
@ -106,7 +106,7 @@ security infrastructure, then you can declare your JAASLoginService in a
top-level jetty xml file as a bean that is added to the top-level jetty xml file as a bean that is added to the
org.eclipse.jetty.server.Server. Here's an example: org.eclipse.jetty.server.Server. Here's an example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure id="Server" class="org.eclipse.jetty.server.Server"> <Configure id="Server" class="org.eclipse.jetty.server.Server">
@ -125,7 +125,7 @@ org.eclipse.jetty.server.Server. Here's an example:
webapp by creating a link:#deployable-descriptor-file[context xml] file webapp by creating a link:#deployable-descriptor-file[context xml] file
for the webapp, and specifying the JAASLoginService in it: for the webapp, and specifying the JAASLoginService in it:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
@ -224,7 +224,7 @@ user role (Default: `org.eclipse.jetty.jaas.JAASRole`)
Here's an example of setting each of these (to their default values): Here's an example of setting each of these (to their default values):
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New class="org.eclipse.jetty.jaas.JAASLoginService"> <New class="org.eclipse.jetty.jaas.JAASLoginService">
<Set name="Name">Test JAAS Realm</Set> <Set name="Name">Test JAAS Realm</Set>
@ -478,7 +478,7 @@ login module, add the RequestParameterCallback to the list of callback
handlers the login module uses, tell it which params you are interested handlers the login module uses, tell it which params you are interested
in, and then get the value of the parameter back. Here's an example: in, and then get the value of the parameter back. Here's an example:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public class FooLoginModule extends AbstractLoginModule public class FooLoginModule extends AbstractLoginModule

72
jetty-documentation/src/main/asciidoc/configuring/security/jetty-home-and-jetty-base.adoc
View File

@ -57,20 +57,20 @@ maximum effect. It also includes a detailed explanation of how modules
work. work.
This example assumes you have the jetty-distribution unpacked in This example assumes you have the jetty-distribution unpacked in
`/home/user/jetty-distribution-@project.version@.` `/home/user/jetty-distribution-{VERSION}.`
1. Create a base directory anywhere. 1. Create a base directory anywhere.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[/home/user]$ mkdir my-base [/home/user]$ mkdir my-base
[/home/user]$ cd my-base [/home/user]$ cd my-base
.... ....
2. Add the modules for SSL, HTTP, and webapp deployment. 2. Add the modules for SSL, HTTP, and webapp deployment.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar --add-to-start=http,https,deploy [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar --add-to-start=http,https,deploy
ssl initialised in ${jetty.base}/start.ini (appended) ssl initialised in ${jetty.base}/start.ini (appended)
ssl enabled in ${jetty.base}/start.ini ssl enabled in ${jetty.base}/start.ini
@ -87,7 +87,7 @@ server enabled in ${jetty.base}/start.ini
.... ....
3. Look at your directory. 3. Look at your directory.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ ls -la [my-base]$ ls -la
total 20 total 20
@ -99,20 +99,20 @@ drwxrwxr-x 2 user group 4096 Oct 8 06:55 webapps/
.... ....
4. Copy your WAR files into webapps. 4. Copy your WAR files into webapps.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ ls -la [my-base]$ ls -la
[my-base]$ cp ~/code/project/target/gadget.war webapps/ [my-base]$ cp ~/code/project/target/gadget.war webapps/
.... ....
5. Copy your keystore into place. 5. Copy your keystore into place.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ cp ~/code/project/keystore etc/keystore [my-base]$ cp ~/code/project/keystore etc/keystore
.... ....
6. Edit the `start.ini` to configure your SSL settings. 6. Edit the `start.ini` to configure your SSL settings.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ cat start.ini [my-base]$ cat start.ini
.... ....
@ -165,9 +165,9 @@ http.timeout=30000
Look at the configuration you have at this point. Look at the configuration you have at this point.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar --list-config [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar --list-config
Java Environment: Java Environment:
----------------- -----------------
@ -182,9 +182,9 @@ Java Environment:
Jetty Environment: Jetty Environment:
----------------- -----------------
jetty.home=/home/user/jetty-distribution-@project.version@ jetty.home=/home/user/jetty-distribution-{VERSION}
jetty.base=/home/user/my-base jetty.base=/home/user/my-base
jetty.version=@project.version@ jetty.version={VERSION}
JVM Arguments: JVM Arguments:
-------------- --------------
@ -193,7 +193,7 @@ JVM Arguments:
System Properties: System Properties:
------------------ ------------------
jetty.base = /home/user/my-base jetty.base = /home/user/my-base
jetty.home = /home/user/jetty-distribution-@project.version@ jetty.home = /home/user/jetty-distribution-{VERSION}
Properties: Properties:
----------- -----------
@ -218,15 +218,15 @@ Note: order presented here is how they would appear on the classpath.
changes to the --module=name command line options will be reflected here. changes to the --module=name command line options will be reflected here.
0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar 0: 3.1.0 | ${jetty.home}/lib/servlet-api-3.1.jar
1: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar 1: 3.1.RC0 | ${jetty.home}/lib/jetty-schemas-3.1.jar
2: @project.version@ | ${jetty.home}/lib/jetty-http-@project.version@.jar 2: {VERSION} | ${jetty.home}/lib/jetty-http-{VERSION}.jar
3: @project.version@ | ${jetty.home}/lib/jetty-continuation-@project.version@.jar 3: {VERSION} | ${jetty.home}/lib/jetty-continuation-{VERSION}.jar
4: @project.version@ | ${jetty.home}/lib/jetty-server-@project.version@.jar 4: {VERSION} | ${jetty.home}/lib/jetty-server-{VERSION}.jar
5: @project.version@ | ${jetty.home}/lib/jetty-xml-@project.version@.jar 5: {VERSION} | ${jetty.home}/lib/jetty-xml-{VERSION}.jar
6: @project.version@ | ${jetty.home}/lib/jetty-util-@project.version@.jar 6: {VERSION} | ${jetty.home}/lib/jetty-util-{VERSION}.jar
7: @project.version@ | ${jetty.home}/lib/jetty-io-@project.version@.jar 7: {VERSION} | ${jetty.home}/lib/jetty-io-{VERSION}.jar
8: @project.version@ | ${jetty.home}/lib/jetty-servlet-@project.version@.jar 8: {VERSION} | ${jetty.home}/lib/jetty-servlet-{VERSION}.jar
9: @project.version@ | ${jetty.home}/lib/jetty-webapp-@project.version@.jar 9: {VERSION} | ${jetty.home}/lib/jetty-webapp-{VERSION}.jar
10: @project.version@ | ${jetty.home}/lib/jetty-deploy-@project.version@.jar 10: {VERSION} | ${jetty.home}/lib/jetty-deploy-{VERSION}.jar
Jetty Active XMLs: Jetty Active XMLs:
------------------ ------------------
@ -238,10 +238,10 @@ Jetty Active XMLs:
Now start Jetty. Now start Jetty.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar
2013-10-08 07:06:55.837:INFO:oejs.Server:main: jetty-@project.version@ 2013-10-08 07:06:55.837:INFO:oejs.Server:main: jetty-{VERSION}
2013-10-08 07:06:55.853:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1 2013-10-08 07:06:55.853:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/my-base/webapps/] at interval 1
2013-10-08 07:06:55.872:INFO:oejs.ServerConnector:main: Started ServerConnector@72974691{HTTP/1.1}{0.0.0.0:8080} 2013-10-08 07:06:55.872:INFO:oejs.ServerConnector:main: Started ServerConnector@72974691{HTTP/1.1}{0.0.0.0:8080}
.... ....
@ -268,9 +268,9 @@ a single unit, with dependencies on other modules.
You can see the list of modules: You can see the list of modules:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar --list-modules [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar --list-modules
Jetty All Available Modules: Jetty All Available Modules:
---------------------------- ----------------------------
@ -458,9 +458,9 @@ easier to edit the `${jetty.base}/start.ini`.
If you want to start using a new module: If you want to start using a new module:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base] $ java -jar ../jetty-distribution-@project.version@/start.jar --add-to-start=https [my-base] $ java -jar ../jetty-distribution-{VERSION}/start.jar --add-to-start=https
.... ....
This adds the `--module=` lines and associated properties (the This adds the `--module=` lines and associated properties (the
@ -494,12 +494,12 @@ For more information on the `start.jar` in 9.1, see xref:start-jar[].
==== Summary of Configuring SSL in Jetty 9.1 ==== Summary of Configuring SSL in Jetty 9.1
1. Download and unpack Jetty 9.1 into 1. Download and unpack Jetty 9.1 into
`/home/user/jetty-distribution-@project.version@`. `/home/user/jetty-distribution-{VERSION}`.
2. Go to your base directory and just use the distribution, no editing. 2. Go to your base directory and just use the distribution, no editing.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar /home/user/jetty-distribution-@project.version@/start.jar [my-base]$ java -jar /home/user/jetty-distribution-{VERSION}/start.jar
.... ....
* The Jetty 9.1 distribution provides, out of the box, the XML * The Jetty 9.1 distribution provides, out of the box, the XML
configuration files, in this case `jetty-http.xml` and `jetty-ssl.xml`. configuration files, in this case `jetty-http.xml` and `jetty-ssl.xml`.
@ -529,9 +529,9 @@ modules as well.
You can see what the configuration looks like, after all of the modules You can see what the configuration looks like, after all of the modules
are resolved, without starting Jetty via: are resolved, without starting Jetty via:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base] $ java -jar ../jetty-distribution-@project.version@/start.jar --list-config [my-base] $ java -jar ../jetty-distribution-{VERSION}/start.jar --list-config
.... ....
Just because the JARs exist on disk does not mean that they are in use. Just because the JARs exist on disk does not mean that they are in use.
@ -541,7 +541,7 @@ Use the `--list-config` to see the configuration. Notice that only a
subset of the JARs from the distribution are in use. The modules you subset of the JARs from the distribution are in use. The modules you
have anabled determine that subset. have anabled determine that subset.
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[my-base]$ java -jar ~/jetty-distribution-@project.version@/start.jar --list-config [my-base]$ java -jar ~/jetty-distribution-{VERSION}/start.jar --list-config
.... ....

6
jetty-documentation/src/main/asciidoc/configuring/security/secure-passwords.adoc
View File

@ -38,7 +38,7 @@ generate all varieties of passwords.
Run it without arguments to see usage instructions: Run it without arguments to see usage instructions:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ export JETTY_VERSION=9.0.0-SNAPSHOT $ export JETTY_VERSION=9.0.0-SNAPSHOT
@ -53,7 +53,7 @@ If the password is ?, the user will be prompted for the password
For example, to generate a secured version of the password "blah" for For example, to generate a secured version of the password "blah" for
the user "me", do: the user "me", do:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ export JETTY_VERSION=9.0.0.RC0 $ export JETTY_VERSION=9.0.0.RC0
@ -93,7 +93,7 @@ You can also use obfuscated passwords in jetty xml files where a plain
text password is usually needed. Here's an example setting the password text password is usually needed. Here's an example setting the password
for a JDBC Datasource with obfuscation: for a JDBC Datasource with obfuscation:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource"> <New id="DSTest" class="org.eclipse.jetty.plus.jndi.Resource">

2
jetty-documentation/src/main/asciidoc/configuring/security/serving-aliased-files.adoc
View File

@ -116,7 +116,7 @@ An application is free to implement its own Alias checking. Alias
Checkers can be installed in a context via the following XML used in a Checkers can be installed in a context via the following XML used in a
context deployer file or `WEB-INF/jetty-web.xml`: context deployer file or `WEB-INF/jetty-web.xml`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<!-- Allow symbolic links --> <!-- Allow symbolic links -->
<Call name="addAliasCheck"> <Call name="addAliasCheck">

10
jetty-documentation/src/main/asciidoc/configuring/security/spnego-support.adoc
View File

@ -59,7 +59,7 @@ helpful:
Spengo Authentication must be enabled in the webapp in the following Spengo Authentication must be enabled in the webapp in the following
way. The name of the role will be different for your network. way. The name of the role will be different for your network.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<security-constraint> <security-constraint>
@ -89,7 +89,7 @@ embedded, via the jetty.xml or in a context file for the webapp.
This is what the configuration within a jetty xml file would look like. This is what the configuration within a jetty xml file would look like.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Call name="addBean"> <Call name="addBean">
@ -107,7 +107,7 @@ This is what the configuration within a jetty xml file would look like.
This is what the configuration within a context xml file would look This is what the configuration within a context xml file would look
like. like.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<Get name="securityHandler"> <Get name="securityHandler">
@ -142,7 +142,7 @@ for the http server. To do this use a process similar to this:
On the windows active domain controller run: On the windows active domain controller run:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ setspn -A HTTP/linux.mortbay.org ADUser $ setspn -A HTTP/linux.mortbay.org ADUser
@ -152,7 +152,7 @@ $ setspn -A HTTP/linux.mortbay.org ADUser
To create the keytab file use the following process: To create the keytab file use the following process:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ ktpass -out c:\dir\krb5.keytab -princ HTTP/linux.mortbay.org@MORTBAY.ORG -mapUser ADUser -mapOp set -pass ADUserPWD -crypto RC4-HMAC-NT -pType KRB5_NT_PRINCIPAL $ ktpass -out c:\dir\krb5.keytab -princ HTTP/linux.mortbay.org@MORTBAY.ORG -mapUser ADUser -mapOp set -pass ADUserPWD -crypto RC4-HMAC-NT -pType KRB5_NT_PRINCIPAL

48
jetty-documentation/src/main/asciidoc/development/ant/jetty-ant.adoc
View File

@ -21,7 +21,7 @@ The Ant Jetty plugin is a part of Jetty 9 under the `jetty-ant` module.
This plugin makes it possible to start a Jetty web server directly from the Ant build script, and to embed the Jetty web server inside your build process. This plugin makes it possible to start a Jetty web server directly from the Ant build script, and to embed the Jetty web server inside your build process.
Its purpose is to provide almost the same functionality as the Jetty plugin for Maven: dynamic application reloading, working directly on web application sources, and tightly integrating with the build system. Its purpose is to provide almost the same functionality as the Jetty plugin for Maven: dynamic application reloading, working directly on web application sources, and tightly integrating with the build system.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>
<groupId>org.eclipse.jetty</groupId> <groupId>org.eclipse.jetty</groupId>
@ -49,7 +49,7 @@ Now you're ready to edit or create your Ant `build.xml` file.
Begin with an empty `build.xml`: Begin with an empty `build.xml`:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
</project> </project>
@ -58,7 +58,7 @@ Begin with an empty `build.xml`:
Add a `<taskdef>` that imports all available Jetty tasks: Add a `<taskdef>` that imports all available Jetty tasks:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -74,7 +74,7 @@ Add a `<taskdef>` that imports all available Jetty tasks:
Now you are ready to add a new target for running Jetty: Now you are ready to add a new target for running Jetty:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -98,7 +98,7 @@ This is the minimal configuration you need. You can now start Jetty on the defau
At the command line enter: At the command line enter:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> ant jetty.run > ant jetty.run
.... ....
@ -111,7 +111,7 @@ ports and connectors:::
To configure the port that Jetty starts on you need to define a connector. To configure the port that Jetty starts on you need to define a connector.
First you need to configure a `<typedef>` for the Connector class and then define the connector in the Jetty tags: First you need to configure a `<typedef>` for the Connector class and then define the connector in the Jetty tags:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -146,7 +146,7 @@ login services:::
If your web application requires authentication and authorization services, you can configure these on the Jetty container. If your web application requires authentication and authorization services, you can configure these on the Jetty container.
Here's an example of how to set up an link:{JDURL}/org/eclipse/jetty/security/HashLoginService.html[org.eclipse.jetty.security.HashLoginService]: Here's an example of how to set up an link:{JDURL}/org/eclipse/jetty/security/HashLoginService.html[org.eclipse.jetty.security.HashLoginService]:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -174,7 +174,7 @@ request log:::
The `requestLog` option allows you to specify a request logger for the Jetty instance. The `requestLog` option allows you to specify a request logger for the Jetty instance.
You can either use the link:{JDURL}/org/eclipse/jetty/server/NCSARequestLog.html[org.eclipse.jetty.server.NCSARequestLog] class, or supply the name of your custom class: You can either use the link:{JDURL}/org/eclipse/jetty/server/NCSARequestLog.html[org.eclipse.jetty.server.NCSARequestLog] class, or supply the name of your custom class:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -195,7 +195,7 @@ request log:::
temporary directory::: temporary directory:::
You can configure a directory as a temporary file store for uses such as expanding files and compiling JSPs by supplying the `tempDirectory` option: You can configure a directory as a temporary file store for uses such as expanding files and compiling JSPs by supplying the `tempDirectory` option:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -218,7 +218,7 @@ other context handlers:::
You can specify these other context handlers using the `<contextHandlers>` element. You can specify these other context handlers using the `<contextHandlers>` element.
You need to supply a `<typedef>` for it before you can use it: You need to supply a `<typedef>` for it before you can use it:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -247,7 +247,7 @@ system properties:::
As a convenience, you can configure system properties by using the `<systemProperties>` element. As a convenience, you can configure system properties by using the `<systemProperties>` element.
Be aware that, depending on the purpose of the system property, setting it from within the Ant execution may mean that it is evaluated too late, as the JVM evaluates some system properties on entry. Be aware that, depending on the purpose of the system property, setting it from within the Ant execution may mean that it is evaluated too late, as the JVM evaluates some system properties on entry.
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -271,7 +271,7 @@ system properties:::
jetty XML file::: jetty XML file:::
If you have a lot of configuration to apply to the Jetty container, it can be more convenient to put it into a standard Jetty XML configuration file and have the Ant plugin apply it before starting Jetty: If you have a lot of configuration to apply to the Jetty container, it can be more convenient to put it into a standard Jetty XML configuration file and have the Ant plugin apply it before starting Jetty:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -295,7 +295,7 @@ scanning for changes:::
The `scanIntervalSeconds` option controls how frequently the `<jetty.run>` task scans your web application/WAR file for changes. The `scanIntervalSeconds` option controls how frequently the `<jetty.run>` task scans your web application/WAR file for changes.
The default value of `0` disables scanning. Here's an example where Jetty checks for changes every five seconds: The default value of `0` disables scanning. Here's an example where Jetty checks for changes every five seconds:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -321,7 +321,7 @@ stopping:::
The `<jetty.stop>` task sends this stop message. The `<jetty.stop>` task sends this stop message.
You can also optionally provide a `stopWait` value (in seconds), which is the length of time the `<jetty.stop>` task waits for confirmation that the stop succeeded: You can also optionally provide a `stopWait` value (in seconds), which is the length of time the `<jetty.stop>` task waits for confirmation that the stop succeeded:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -346,7 +346,7 @@ stopping:::
+ +
To stop jetty via Ant, enter: To stop jetty via Ant, enter:
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> ant jetty.stop > ant jetty.stop
.... ....
@ -359,7 +359,7 @@ execution without pausing ant:::
This defaults to `false`. For `true`, Ant continues to execute after starting Jetty. This defaults to `false`. For `true`, Ant continues to execute after starting Jetty.
If Ant exits, so does Jetty. Understand that this option does _not_ fork a new process for Jetty. If Ant exits, so does Jetty. Understand that this option does _not_ fork a new process for Jetty.
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -383,7 +383,7 @@ execution without pausing ant:::
Add a `<typedef>` for the `org.eclipse.jetty.ant.AntWebAppContext` class with name __webApp__, then add a `<webApp>` element to `<jetty.run>` to describe your web application. Add a `<typedef>` for the `org.eclipse.jetty.ant.AntWebAppContext` class with name __webApp__, then add a `<webApp>` element to `<jetty.run>` to describe your web application.
The following example deploys a web application that is expanded in the local directory `foo/` to context path ` / `: The following example deploys a web application that is expanded in the local directory `foo/` to context path ` / `:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -410,7 +410,7 @@ deploying a WAR file:::
It is not necessary to expand the web application into a directory. It is not necessary to expand the web application into a directory.
It is fine to deploy it as a WAR file: It is fine to deploy it as a WAR file:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -436,7 +436,7 @@ deploying a WAR file:::
deploying more than one web application::: deploying more than one web application:::
You can also deploy more than one web application: You can also deploy more than one web application:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -471,7 +471,7 @@ class, you can configure it by adding attributes of the same name
Here's an example that specifies the location of the `web.xml` file (equivalent to method link:{JDURL}/org/eclipse/jetty/webapp/WebAppContext.html#setDescriptor%28java.lang.String%29[`AntWebAppContext.setDescriptor()`]) and the web application's temporary directory (equivalent to method link:{JDURL}/org/eclipse/jetty/webapp/WebAppContext.html#setTempDirectory%28java.io.File%29[`AntWebAppContext.setTempDirectory()`]): Here's an example that specifies the location of the `web.xml` file (equivalent to method link:{JDURL}/org/eclipse/jetty/webapp/WebAppContext.html#setDescriptor%28java.lang.String%29[`AntWebAppContext.setDescriptor()`]) and the web application's temporary directory (equivalent to method link:{JDURL}/org/eclipse/jetty/webapp/WebAppContext.html#setTempDirectory%28java.io.File%29[`AntWebAppContext.setTempDirectory()`]):
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -499,7 +499,7 @@ Other extra configuration options for the AntWebAppContext include:
extra classes and Jars::: extra classes and Jars:::
If your web application's classes and Jars do not reside inside `WEB-INF` of the resource base directory, you can use the <classes> and <jar> elements to tell Ant where to find them. Here's an example: If your web application's classes and Jars do not reside inside `WEB-INF` of the resource base directory, you can use the <classes> and <jar> elements to tell Ant where to find them. Here's an example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -536,7 +536,7 @@ context attributes:::
For convenience, the Ant plugin permits you to configure these directly in the build file. For convenience, the Ant plugin permits you to configure these directly in the build file.
Here's an example: Here's an example:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -565,7 +565,7 @@ context attributes:::
`jetty-env.xml` file::: `jetty-env.xml` file:::
If you are using features such as link:#configuring_jndi[JNDI] with your web application, you may need to configure a link:#using_jndi[`WEB-INF/jetty-env.xml`] file to define resources. If the structure of your web application project is such that the source of `jetty-env.xml` file resides somewhere other than `WEB-INF`, you can use the `jettyEnvXml` attribute to tell Ant where to find it: If you are using features such as link:#configuring_jndi[JNDI] with your web application, you may need to configure a link:#using_jndi[`WEB-INF/jetty-env.xml`] file to define resources. If the structure of your web application project is such that the source of `jetty-env.xml` file resides somewhere other than `WEB-INF`, you can use the `jettyEnvXml` attribute to tell Ant where to find it:
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<project name="Jetty-Ant integration test" basedir="."> <project name="Jetty-Ant integration test" basedir=".">
@ -594,7 +594,7 @@ context XML file:::
In this case, you can use a standard context XML configuration file which the Ant plugin applies to your web application before it is deployed. In this case, you can use a standard context XML configuration file which the Ant plugin applies to your web application before it is deployed.
Be aware that the settings from the context XML file _override_ those of the attributes and nested elements you defined in the build file. Be aware that the settings from the context XML file _override_ those of the attributes and nested elements you defined in the build file.
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
project name="Jetty-Ant integration test" basedir="."> project name="Jetty-Ant integration test" basedir=".">

40
jetty-documentation/src/main/asciidoc/development/clients/http/http-client-api.adoc
View File

@ -22,7 +22,7 @@
The simpler way to perform a HTTP request is the following: The simpler way to perform a HTTP request is the following:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.GET("http://domain.com/path?query"); ContentResponse response = httpClient.GET("http://domain.com/path?query");
@ -36,7 +36,7 @@ The content length is limited by default to 2 MiB; for larger content see xref:h
If you want to customize the request, for example by issuing a HEAD request instead of a GET, and simulating a browser user agent, you can do it in this way: If you want to customize the request, for example by issuing a HEAD request instead of a GET, and simulating a browser user agent, you can do it in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/path?query") ContentResponse response = httpClient.newRequest("http://domain.com/path?query")
.method(HttpMethod.HEAD) .method(HttpMethod.HEAD)
@ -48,7 +48,7 @@ ContentResponse response = httpClient.newRequest("http://domain.com/path?query")
This is a shorthand for: This is a shorthand for:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Request request = httpClient.newRequest("http://domain.com/path?query"); Request request = httpClient.newRequest("http://domain.com/path?query");
@ -64,7 +64,7 @@ When the request object is customized, you call `Request.send()` that produces t
Simple POST requests also have a shortcut method: Simple POST requests also have a shortcut method:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.POST("http://domain.com/entity/1") ContentResponse response = httpClient.POST("http://domain.com/entity/1")
@ -81,7 +81,7 @@ Following redirects is a feature that you can enable/disable on a per-request ba
File uploads also require one line, and make use of JDK 7′s `java.nio.file` classes: File uploads also require one line, and make use of JDK 7′s `java.nio.file` classes:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/upload") ContentResponse response = httpClient.newRequest("http://domain.com/upload")
@ -93,7 +93,7 @@ ContentResponse response = httpClient.newRequest("http://domain.com/upload")
It is possible to impose a total timeout for the request/response conversation using the `Request.timeout(...)` method, in this way: It is possible to impose a total timeout for the request/response conversation using the `Request.timeout(...)` method, in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/path?query") ContentResponse response = httpClient.newRequest("http://domain.com/path?query")
@ -135,7 +135,7 @@ When the request and the response are both fully processed, the thread that fini
A simple asynchronous GET request that discards the response content can be written in this way: A simple asynchronous GET request that discards the response content can be written in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.newRequest("http://domain.com/path") httpClient.newRequest("http://domain.com/path")
@ -155,7 +155,7 @@ Method `Request.send(Response.CompleteListener)` returns void and does not block
You can write the same code using JDK 8′s lambda expressions: You can write the same code using JDK 8′s lambda expressions:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.newRequest("http://domain.com/path") httpClient.newRequest("http://domain.com/path")
@ -166,7 +166,7 @@ httpClient.newRequest("http://domain.com/path")
You can impose a total timeout for the request/response conversation in the same way used by the synchronous API: You can impose a total timeout for the request/response conversation in the same way used by the synchronous API:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Request request = httpClient.newRequest("http://domain.com/path") Request request = httpClient.newRequest("http://domain.com/path")
@ -187,7 +187,7 @@ The example above will impose a total timeout of 3 seconds on the request/respon
The HTTP client APIs use listeners extensively to provide hooks for all possible request and response events, and with JDK 8′s lambda expressions they’re even more fun to use: The HTTP client APIs use listeners extensively to provide hooks for all possible request and response events, and with JDK 8′s lambda expressions they’re even more fun to use:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.newRequest("http://domain.com/path") httpClient.newRequest("http://domain.com/path")
@ -222,7 +222,7 @@ Jetty HTTP client provides a number of utility classes off the shelf to handle r
You can provide request content as `String`, `byte[]`, `ByteBuffer`, `java.nio.file.Path`, `InputStream`, and provide your own implementation of `org.eclipse.jetty.client.api.ContentProvider`. You can provide request content as `String`, `byte[]`, `ByteBuffer`, `java.nio.file.Path`, `InputStream`, and provide your own implementation of `org.eclipse.jetty.client.api.ContentProvider`.
Here’s an example that provides the request content using `java.nio.file.Paths`: Here’s an example that provides the request content using `java.nio.file.Paths`:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/upload") ContentResponse response = httpClient.newRequest("http://domain.com/upload")
@ -234,7 +234,7 @@ ContentResponse response = httpClient.newRequest("http://domain.com/upload")
This is equivalent to using the `PathContentProvider` utility class: This is equivalent to using the `PathContentProvider` utility class:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/upload") ContentResponse response = httpClient.newRequest("http://domain.com/upload")
@ -246,7 +246,7 @@ ContentResponse response = httpClient.newRequest("http://domain.com/upload")
Alternatively, you can use `FileInputStream` via the `InputStreamContentProvider` utility class: Alternatively, you can use `FileInputStream` via the `InputStreamContentProvider` utility class:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient.newRequest("http://domain.com/upload") ContentResponse response = httpClient.newRequest("http://domain.com/upload")
@ -260,7 +260,7 @@ Since `InputStream` is blocking, then also the send of the request will block if
If you have already read the content in memory, you can pass it as a `byte[]` using the `BytesContentProvider` utility class: If you have already read the content in memory, you can pass it as a `byte[]` using the `BytesContentProvider` utility class:
[source,java] [source, java, subs="{sub-order}"]
---- ----
byte[] bytes = ...; byte[] bytes = ...;
@ -273,7 +273,7 @@ ContentResponse response = httpClient.newRequest("http://domain.com/upload")
If the request content is not immediately available, but your application will be notified of the content to send, you can use `DeferredContentProvider` in this way: If the request content is not immediately available, but your application will be notified of the content to send, you can use `DeferredContentProvider` in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
DeferredContentProvider content = new DeferredContentProvider(); DeferredContentProvider content = new DeferredContentProvider();
@ -309,7 +309,7 @@ This allows fine-grained control of the request/response conversation: for examp
Another way to provide request content is by using an `OutputStreamContentProvider`, which allows applications to write request content when it is available to the `OutputStream` provided by `OutputStreamContentProvider`: Another way to provide request content is by using an `OutputStreamContentProvider`, which allows applications to write request content when it is available to the `OutputStream` provided by `OutputStreamContentProvider`:
[source,java] [source, java, subs="{sub-order}"]
---- ----
OutputStreamContentProvider content = new OutputStreamContentProvider(); OutputStreamContentProvider content = new OutputStreamContentProvider();
@ -347,7 +347,7 @@ The first way is to buffer the response content in memory; this is done when usi
If you want to control the length of the response content (for example limiting to values smaller than the default of 2 MiB), then you can use a `org.eclipse.jetty.client.util.FutureResponseListener`in this way: If you want to control the length of the response content (for example limiting to values smaller than the default of 2 MiB), then you can use a `org.eclipse.jetty.client.util.FutureResponseListener`in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
Request request = httpClient.newRequest("http://domain.com/path"); Request request = httpClient.newRequest("http://domain.com/path");
@ -366,7 +366,7 @@ If the response content length is exceeded, the response will be aborted, and an
If you are using the asynchronous APIs (see xref:http-client-async[]), you can use the `BufferingResponseListener` utility class: If you are using the asynchronous APIs (see xref:http-client-async[]), you can use the `BufferingResponseListener` utility class:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.newRequest("http://domain.com/path") httpClient.newRequest("http://domain.com/path")
@ -389,7 +389,7 @@ httpClient.newRequest("http://domain.com/path")
The second way is the most efficient (because it avoids content copies) and allows you to specify a `Response.ContentListener`, or a subclass, to handle the content as soon as it arrives: The second way is the most efficient (because it avoids content copies) and allows you to specify a `Response.ContentListener`, or a subclass, to handle the content as soon as it arrives:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ContentResponse response = httpClient ContentResponse response = httpClient
@ -408,7 +408,7 @@ ContentResponse response = httpClient
The third way allows you to wait for the response and then stream the content using the `InputStreamResponseListener` utility class: The third way allows you to wait for the response and then stream the content using the `InputStreamResponseListener` utility class:
[source,java] [source, java, subs="{sub-order}"]
---- ----
InputStreamResponseListener listener = new InputStreamResponseListener(); InputStreamResponseListener listener = new InputStreamResponseListener();

4
jetty-documentation/src/main/asciidoc/development/clients/http/http-client-intro.adoc
View File

@ -42,7 +42,7 @@ Like a browser, it can make requests to different domains, it manages redirects,
In order to use `HttpClient`, you must instantiate it, configure it, and then start it: In order to use `HttpClient`, you must instantiate it, configure it, and then start it:
[source,java] [source, java, subs="{sub-order}"]
---- ----
// Instantiate HttpClient // Instantiate HttpClient
@ -64,7 +64,7 @@ When you create a `HttpClient` instance using the parameterless constructor, you
In order to perform HTTPS requests, you should create first a link:{JDURL}/org/eclipse/jetty/util/ssl/SslContextFactory.html[`SslContextFactory`], configure it, and pass it to `HttpClient`'s constructor. In order to perform HTTPS requests, you should create first a link:{JDURL}/org/eclipse/jetty/util/ssl/SslContextFactory.html[`SslContextFactory`], configure it, and pass it to `HttpClient`'s constructor.
When created with a `SslContextFactory`, the `HttpClient` will be able to perform both HTTP and HTTPS requests to any domain. When created with a `SslContextFactory`, the `HttpClient` will be able to perform both HTTP and HTTPS requests to any domain.
[source,java] [source, java, subs="{sub-order}"]
---- ----
// Instantiate and configure the SslContextFactory // Instantiate and configure the SslContextFactory

16
jetty-documentation/src/main/asciidoc/development/clients/http/http-client-other.adoc
View File

@ -26,7 +26,7 @@ When new requests are made, the cookie store is consulted and if there are match
Applications can programmatically access the cookie store to find the cookies that have been set: Applications can programmatically access the cookie store to find the cookies that have been set:
[source,java] [source, java, subs="{sub-order}"]
---- ----
CookieStore cookieStore = httpClient.getCookieStore(); CookieStore cookieStore = httpClient.getCookieStore();
@ -37,7 +37,7 @@ List<HttpCookie> cookies = cookieStore.get(URI.create("http://domain.com/path"))
Applications can also programmatically set cookies as if they were returned from a HTTP response: Applications can also programmatically set cookies as if they were returned from a HTTP response:
[source,java] [source, java, subs="{sub-order}"]
---- ----
CookieStore cookieStore = httpClient.getCookieStore(); CookieStore cookieStore = httpClient.getCookieStore();
@ -52,7 +52,7 @@ cookieStore.add(URI.create("http://domain.com"), cookie);
You can remove cookies that you do not want to be sent in future HTTP requests: You can remove cookies that you do not want to be sent in future HTTP requests:
[source,java] [source, java, subs="{sub-order}"]
---- ----
CookieStore cookieStore = httpClient.getCookieStore(); CookieStore cookieStore = httpClient.getCookieStore();
@ -66,7 +66,7 @@ for (HttpCookie cookie : cookies)
If you want to totally disable cookie handling, you can install a `HttpCookieStore.Empty` instance in this way: If you want to totally disable cookie handling, you can install a `HttpCookieStore.Empty` instance in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.setCookieStore(new HttpCookieStore.Empty()); httpClient.setCookieStore(new HttpCookieStore.Empty());
@ -76,7 +76,7 @@ httpClient.setCookieStore(new HttpCookieStore.Empty());
You can enable cookie filtering by installing a cookie store that performs the filtering logic in this way: You can enable cookie filtering by installing a cookie store that performs the filtering logic in this way:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.setCookieStore(new GoogleOnlyCookieStore()); httpClient.setCookieStore(new GoogleOnlyCookieStore());
@ -103,7 +103,7 @@ Jetty HTTP client supports the "Basic" and "Digest" authentication mechanisms de
You can configure authentication credentials in the HTTP client instance as follows: You can configure authentication credentials in the HTTP client instance as follows:
[source,java] [source, java, subs="{sub-order}"]
---- ----
URI uri = new URI("http://domain.com/secure"); URI uri = new URI("http://domain.com/secure");
@ -128,7 +128,7 @@ If the authentication is successful, it caches the result and reuses it for subs
Successful authentications are cached, but it is possible to clear them in order to force authentication again: Successful authentications are cached, but it is possible to clear them in order to force authentication again:
[source,java] [source, java, subs="{sub-order}"]
---- ----
httpClient.getAuthenticationStore().clearAuthenticationResults(); httpClient.getAuthenticationStore().clearAuthenticationResults();
@ -146,7 +146,7 @@ Other implementations may be written by subclassing `ProxyConfiguration.Proxy`.
A typical configuration is the following: A typical configuration is the following:
[source,java] [source, java, subs="{sub-order}"]
---- ----
ProxyConfiguration proxyConfig = httpClient.getProxyConfiguration(); ProxyConfiguration proxyConfig = httpClient.getProxyConfiguration();

4
jetty-documentation/src/main/asciidoc/development/continuations/continuations-patterns.adoc
View File

@ -22,7 +22,7 @@
The suspend/resume style is used when a servlet and/or filter is used to generate the response after an asynchronous wait that is terminated by an asynchronous handler. The suspend/resume style is used when a servlet and/or filter is used to generate the response after an asynchronous wait that is terminated by an asynchronous handler.
Typically a request attribute is used to pass results and to indicate if the request has already been suspended. Typically a request attribute is used to pass results and to indicate if the request has already been suspended.
[source,java] [source, java, subs="{sub-order}"]
---- ----
void doGet(HttpServletRequest request, HttpServletResponse response) void doGet(HttpServletRequest request, HttpServletResponse response)
{ {
@ -67,7 +67,7 @@ This style is very good when the response needs the facilities of the servlet co
The suspend/complete style is used when an asynchronous handler is used to generate the response: The suspend/complete style is used when an asynchronous handler is used to generate the response:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void doGet(HttpServletRequest request, HttpServletResponse response) void doGet(HttpServletRequest request, HttpServletResponse response)
{ {

8
jetty-documentation/src/main/asciidoc/development/continuations/continuations-using.adoc
View File

@ -31,7 +31,7 @@ The link:{JDURL}/org/eclipse/jetty/continuation/ContinuationSupport.html[Continu
To suspend a request, the suspend method can be called on the continuation: To suspend a request, the suspend method can be called on the continuation:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void doGet(HttpServletRequest request, HttpServletResponse response) void doGet(HttpServletRequest request, HttpServletResponse response)
{ {
@ -60,7 +60,7 @@ If an exception is desirable (to bypass code that is unaware of continuations an
Once an asynchronous event has occurred, the continuation can be resumed: Once an asynchronous event has occurred, the continuation can be resumed:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void myAsyncCallback(Object results) void myAsyncCallback(Object results)
{ {
@ -78,7 +78,7 @@ Continuation resume is analogous to Servlet 3.0 `AsyncContext.dispatch()`.
As an alternative to resuming a request, an asynchronous handler may write the response itself. After writing the response, the handler must indicate the request handling is complete by calling the complete method: As an alternative to resuming a request, an asynchronous handler may write the response itself. After writing the response, the handler must indicate the request handling is complete by calling the complete method:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void myAsyncCallback(Object results) void myAsyncCallback(Object results)
{ {
@ -93,7 +93,7 @@ After complete is called, the container schedules the response to be committed
An application may monitor the status of a continuation by using a ContinuationListener: An application may monitor the status of a continuation by using a ContinuationListener:
[source,java] [source, java, subs="{sub-order}"]
---- ----
void doGet(HttpServletRequest request, HttpServletResponse response) void doGet(HttpServletRequest request, HttpServletResponse response)
{ {

6
jetty-documentation/src/main/asciidoc/development/debugging/enable-remote-debugging.adoc
View File

@ -36,7 +36,7 @@ Assuming you have your webapp deployed into jetty, there are two different ways
Via command line:: Via command line::
Add the required parameters on the commandline like so. Add the required parameters on the commandline like so.
+ +
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ java -Xdebug -agentlib:jdwp=transport=dt_socket,address=9999,server=y,suspend=n -jar start.jar $ java -Xdebug -agentlib:jdwp=transport=dt_socket,address=9999,server=y,suspend=n -jar start.jar
@ -50,7 +50,7 @@ Via `start.ini`::
1. Edit the `start.ini` and uncomment the --exec line, this is required if you are adding jvm options to the start.ini file as jetty-start must generate the classpath required and fork a new jvm. 1. Edit the `start.ini` and uncomment the --exec line, this is required if you are adding jvm options to the start.ini file as jetty-start must generate the classpath required and fork a new jvm.
2. Add the parameters mentioned above in the Command Line option so your start.ini looks like this: 2. Add the parameters mentioned above in the Command Line option so your start.ini looks like this:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
#=========================================================== #===========================================================
# Configure JVM arguments. # Configure JVM arguments.
@ -84,7 +84,7 @@ Uncomment any other jvm environmental options you so desire for your debugging s
3. Regardless of the option chosen, you should see the following lines at the top of your jetty-distribution startup. 3. Regardless of the option chosen, you should see the following lines at the top of your jetty-distribution startup.
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Listening for transport dt_socket at address: 9999 Listening for transport dt_socket at address: 9999

4
jetty-documentation/src/main/asciidoc/development/embedding/embedded-examples.adoc
View File

@ -40,7 +40,7 @@ This example is very similar to the one in the previous section, although it ena
As of jetty-9.2, we use the JSP engine from Apache, which relies on a Servlet Specification 3.1 style ServletContainerInitializer to initialize itself. As of jetty-9.2, we use the JSP engine from Apache, which relies on a Servlet Specification 3.1 style ServletContainerInitializer to initialize itself.
To get this to work with Jetty, you need to enable annotations processing, as shown in this example code: To get this to work with Jetty, you need to enable annotations processing, as shown in this example code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebAppWithJsp.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebAppWithJsp.java[]
@ -54,7 +54,7 @@ After you have started things up you should be able to navigate to http://localh
To use this example in your project, you will need the following maven dependencies declared, in addition to those from the previous section: To use this example in your project, you will need the following maven dependencies declared, in addition to those from the previous section:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

18
jetty-documentation/src/main/asciidoc/development/embedding/embedding-jetty.adoc
View File

@ -78,7 +78,7 @@ The handler sets the response status, content-type, and marks the request as han
To allow a Handler to handle HTTP requests, you must add it to a Server instance. To allow a Handler to handle HTTP requests, you must add it to a Server instance.
The following code from OneHandler.java shows how a Jetty server can use the HelloWorld handler: The following code from OneHandler.java shows how a Jetty server can use the HelloWorld handler:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneHandler.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneHandler.java[]
---- ----
@ -130,7 +130,7 @@ Thus when the ContextHandler handles the request, it does so within the scope th
The link:{JXURL}/org/eclipse/jetty/embedded/FileServer.html[FileServer example] shows how you can use a ResourceHandler to serve static content from the current working directory: The link:{JXURL}/org/eclipse/jetty/embedded/FileServer.html[FileServer example] shows how you can use a ResourceHandler to serve static content from the current working directory:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/FileServer.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/FileServer.java[]
---- ----
@ -147,7 +147,7 @@ However, often when embedding Jetty it is desirable to explicity instantiate and
The following example, link:{JXURL}/org/eclipse/jetty/embedded/OneConnector.html[OneConnector.java], The following example, link:{JXURL}/org/eclipse/jetty/embedded/OneConnector.html[OneConnector.java],
instantiates, configures, and adds a single HTTP connector instance to the server: instantiates, configures, and adds a single HTTP connector instance to the server:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneConnector.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneConnector.java[]
---- ----
@ -171,7 +171,7 @@ It uses standard path mappings to match a Servlet to a request; sets the request
The link:{JXURL}/org/eclipse/jetty/embedded/MinimalServlets.html[MinimalServlets example] creates a ServletHandler instance and configures a single HelloServlet: The link:{JXURL}/org/eclipse/jetty/embedded/MinimalServlets.html[MinimalServlets example] creates a ServletHandler instance and configures a single HelloServlet:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/MinimalServlets.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/MinimalServlets.java[]
---- ----
@ -189,7 +189,7 @@ Requests that match the context path have their path methods updated accordingly
The following link:{JXURL}/org/eclipse/jetty/embedded/OneContext.html[OneContext example] shows a context being established that wraps the link:{JXURL}/org/eclipse/jetty/embedded/HelloHandler.html[HelloHandler]: The following link:{JXURL}/org/eclipse/jetty/embedded/OneContext.html[OneContext example] shows a context being established that wraps the link:{JXURL}/org/eclipse/jetty/embedded/HelloHandler.html[HelloHandler]:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneContext.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneContext.java[]
---- ----
@ -197,7 +197,7 @@ include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/One
When many contexts are present, you can embed a ContextHandlerCollection to efficiently examine a request URI to then select the matching ContextHandler(s) for the request. When many contexts are present, you can embed a ContextHandlerCollection to efficiently examine a request URI to then select the matching ContextHandler(s) for the request.
The link:{JXURL}/org/eclipse/jetty/embedded/ManyContexts.html[ManyContexts example] shows how many such contexts you can configure: The link:{JXURL}/org/eclipse/jetty/embedded/ManyContexts.html[ManyContexts example] shows how many such contexts you can configure:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ManyContexts.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ManyContexts.java[]
---- ----
@ -207,7 +207,7 @@ include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/Man
A link:{JXURL}/org/eclipse/jetty/servlet/ServletContextHandler.html[ServletContextHandler] is a specialization of ContextHandler with support for standard sessions and Servlets. A link:{JXURL}/org/eclipse/jetty/servlet/ServletContextHandler.html[ServletContextHandler] is a specialization of ContextHandler with support for standard sessions and Servlets.
The following link:{JXURL}/org/eclipse/jetty/embedded/OneServletContext.html[OneServletContext example] instantiates a link:{JXURL}/org/eclipse/jetty/servlet/DefaultServlet.html[DefaultServlet] to server static content from /tmp/ and a `DumpServlet` that creates a session and dumps basic details about the request: The following link:{JXURL}/org/eclipse/jetty/embedded/OneServletContext.html[OneServletContext example] instantiates a link:{JXURL}/org/eclipse/jetty/servlet/DefaultServlet.html[DefaultServlet] to server static content from /tmp/ and a `DumpServlet` that creates a session and dumps basic details about the request:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneServletContext.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneServletContext.java[]
---- ----
@ -218,7 +218,7 @@ A link:{JXURL}/org/eclipse/jetty/webapp/WebAppContext.html[WebAppContext] is an
The following link:{JXURL}/org/eclipse/jetty/embedded/OneWebApp.html[OneWebApp example] configures the Jetty test webapp. The following link:{JXURL}/org/eclipse/jetty/embedded/OneWebApp.html[OneWebApp example] configures the Jetty test webapp.
Web applications can use resources the container provides, and in this case a LoginService is needed and also configured: Web applications can use resources the container provides, and in this case a LoginService is needed and also configured:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebApp.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebApp.java[]
---- ----
@ -239,7 +239,7 @@ The link:{JXURL}/org/eclipse/jetty/embedded/LikeJettyXml.html[LikeJettyXml examp
* link:{GITBROWSEURL}/jetty-server/src/main/config/etc/jetty-lowresources.xml[jetty-lowresources.xml] * link:{GITBROWSEURL}/jetty-server/src/main/config/etc/jetty-lowresources.xml[jetty-lowresources.xml]
* link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/config/etc/test-realm.xml[test-realm.xml] * link:{GITBROWSEURL}/tests/test-webapps/test-jetty-webapp/src/main/config/etc/test-realm.xml[test-realm.xml]
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/LikeJettyXml.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/LikeJettyXml.java[]
---- ----

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-file-server.adoc
View File

@ -22,7 +22,7 @@ It is perfectly suitable for test cases where you need an actual web server to o
Note that this does not have any logic for caching of files, either within the server or setting the appropriate headers on the response. Note that this does not have any logic for caching of files, either within the server or setting the appropriate headers on the response.
It is simply a few lines that illustrate how easy it is to serve out some files. It is simply a few lines that illustrate how easy it is to serve out some files.
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/FileServer.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/FileServer.java[]
@ -36,7 +36,7 @@ After you have started things up you should be able to navigate to http://localh
To use this example in your project you will need the following maven dependencies declared. To use this example in your project you will need the following maven dependencies declared.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>
<groupId>org.eclipse.jetty</groupId> <groupId>org.eclipse.jetty</groupId>

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-many-connectors.adoc
View File

@ -20,7 +20,7 @@
This example shows how to configure Jetty to use multiple connectors, specifically so it can process both http and https requests. This example shows how to configure Jetty to use multiple connectors, specifically so it can process both http and https requests.
Since the meat of this example is the server and connector configuration it only uses a simple HelloHandler but this example should be easily merged with other examples like those deploying servlets or webapps. Since the meat of this example is the server and connector configuration it only uses a simple HelloHandler but this example should be easily merged with other examples like those deploying servlets or webapps.
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ManyConnectors.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ManyConnectors.java[]
@ -36,7 +36,7 @@ See http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Thread.html#join()[Th
To use this example in your project you will need the following maven dependencies declared. To use this example in your project you will need the following maven dependencies declared.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-minimal-servlet.adoc
View File

@ -22,7 +22,7 @@ Note that this is strictly a servlet, not a servlet in the context of a web appl
This is purely just a servlet deployed and mounted on a context and able to process requests. This is purely just a servlet deployed and mounted on a context and able to process requests.
This example is excellent for situations where you have a simple servlet that you need to unit test, just mount it on a context and issue requests using your favorite http client library (like our Jetty client found in xref:http-client[]). This example is excellent for situations where you have a simple servlet that you need to unit test, just mount it on a context and issue requests using your favorite http client library (like our Jetty client found in xref:http-client[]).
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/MinimalServlets.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/MinimalServlets.java[]
@ -41,7 +41,7 @@ After you have started things up you should be able to navigate to http://localh
To use this example in your project you will need the following maven dependencies declared. To use this example in your project you will need the following maven dependencies declared.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-one-webapp.adoc
View File

@ -21,7 +21,7 @@ This example shows how to deploy a simple webapp with an embedded instance of je
This is useful when you want to manage the lifecycle of a server programmatically, either within a production application or as a simple way to deploying and debugging a full scale application deployment. This is useful when you want to manage the lifecycle of a server programmatically, either within a production application or as a simple way to deploying and debugging a full scale application deployment.
In many ways it is easier then traditional deployment since you control the classpath yourself, making this easy to wire up in a test case in maven and issue requests using your favorite http client library (like our Jetty client found in xref:http-client[]). In many ways it is easier then traditional deployment since you control the classpath yourself, making this easy to wire up in a test case in maven and issue requests using your favorite http client library (like our Jetty client found in xref:http-client[]).
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebApp.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/OneWebApp.java[]
@ -35,7 +35,7 @@ After you have started things up you should be able to navigate to http://localh
To use this example in your project you will need the following maven dependencies declared. To use this example in your project you will need the following maven dependencies declared.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-secured-hello-handler.adoc
View File

@ -22,7 +22,7 @@ We have a simple Hello Handler that just return a greeting but add on the restri
Another thing to remember is that this example uses the ConstraintSecurityHandler which is what supports the security mappings inside of the servlet api, it could be easier to show just the SecurityHandler usage, but the constraint provides more configuration power. Another thing to remember is that this example uses the ConstraintSecurityHandler which is what supports the security mappings inside of the servlet api, it could be easier to show just the SecurityHandler usage, but the constraint provides more configuration power.
If you don't need that you can drop the Constraint bits and use just the SecurityHandler. If you don't need that you can drop the Constraint bits and use just the SecurityHandler.
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SecuredHelloHandler.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SecuredHelloHandler.java[]
@ -44,7 +44,7 @@ include::{SRCDIR}/examples/embedded/src/test/resources/realm.properties[]
To use this example in your project you will need the following maven dependencies declared. To use this example in your project you will need the following maven dependencies declared.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

4
jetty-documentation/src/main/asciidoc/development/embedding/examples/embedded-split-file-server.adoc
View File

@ -19,7 +19,7 @@
This example builds on the link:#emebedded-file-server[Simple File Server] to show how chaining multiple ResourceHandlers together can let you aggregate mulitple directories to serve content on a single path and how you can link these together with ContextHandlers. This example builds on the link:#emebedded-file-server[Simple File Server] to show how chaining multiple ResourceHandlers together can let you aggregate mulitple directories to serve content on a single path and how you can link these together with ContextHandlers.
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SplitFileServer.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/SplitFileServer.java[]
@ -36,7 +36,7 @@ Any requests for files will be looked for in the first resource handler, then th
To use this example as is in your project you will need the following maven dependencies declared. To use this example as is in your project you will need the following maven dependencies declared.
We would recommend not using the toolchain dependency in your actual application. We would recommend not using the toolchain dependency in your actual application.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<dependency> <dependency>

12
jetty-documentation/src/main/asciidoc/development/embedding/jetty-helloworld.adoc
View File

@ -24,7 +24,7 @@ This section provides a tutorial that shows how you can quickly develop embedded
Jetty is decomposed into many jars and dependencies to achieve a minimal footprint by selecting the minimal set of jars. Jetty is decomposed into many jars and dependencies to achieve a minimal footprint by selecting the minimal set of jars.
Typically it is best to use something like Maven to manage jars, however this tutorial uses an aggregate Jar that contains all of the Jetty classes in one Jar. Typically it is best to use something like Maven to manage jars, however this tutorial uses an aggregate Jar that contains all of the Jetty classes in one Jar.
You can manually download the aggregate http://central.maven.org/maven2/org/eclipse/jetty/aggregate/jetty-all/@project.version@/jetty-all-@project.version@-uber.jar[`jetty-all.jar`] using `curl`) or a browser. You can manually download the aggregate http://central.maven.org/maven2/org/eclipse/jetty/aggregate/jetty-all/{VERSION}/jetty-all-{VERSION}-uber.jar[`jetty-all.jar`] using `curl`) or a browser.
____ ____
[NOTE] [NOTE]
@ -34,11 +34,11 @@ ____
Use curl as follows: Use curl as follows:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> mkdir Demo > mkdir Demo
> cd Demo > cd Demo
> curl -o jetty-all-uber.jar http://central.maven.org/maven2/org/eclipse/jetty/aggregate/jetty-all/@project.version@/jetty-all-@project.version@-uber.jar > curl -o jetty-all-uber.jar http://central.maven.org/maven2/org/eclipse/jetty/aggregate/jetty-all/{VERSION}/jetty-all-{VERSION}-uber.jar
.... ....
[[writing-helloworld-example]] [[writing-helloworld-example]]
@ -48,7 +48,7 @@ The link:#embedding[Embedding Jetty] section contains many examples of writing a
This tutorial uses a simple HelloWorld handler with a main method to run the server. This tutorial uses a simple HelloWorld handler with a main method to run the server.
You can either link:{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/HelloWorld.java[download] or create in an editor the file `HelloWorld.java` with the following content: You can either link:{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/HelloWorld.java[download] or create in an editor the file `HelloWorld.java` with the following content:
[source,java] [source, java, subs="{sub-order}"]
---- ----
include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/HelloWorld.java[] include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/HelloWorld.java[]
---- ----
@ -58,7 +58,7 @@ include::{SRCDIR}/examples/embedded/src/main/java/org/eclipse/jetty/embedded/Hel
The following command compiles the HelloWorld class: The following command compiles the HelloWorld class:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> mkdir classes > mkdir classes
> javac -d classes -cp jetty-all-uber.jar HelloWorld.java > javac -d classes -cp jetty-all-uber.jar HelloWorld.java
@ -69,7 +69,7 @@ The following command compiles the HelloWorld class:
The following command runs the HelloWorld example: The following command runs the HelloWorld example:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
> java -cp classes:jetty-all-uber.jar org.eclipse.jetty.embedded.HelloWorld > java -cp classes:jetty-all-uber.jar org.eclipse.jetty.embedded.HelloWorld
.... ....

6
jetty-documentation/src/main/asciidoc/development/frameworks/metro.adoc
View File

@ -29,7 +29,7 @@ We'll refer to the unpacked location as `$metro.home`.
3. Copy the jars from $metro.home/lib to `$jetty.home/lib/metro` 3. Copy the jars from $metro.home/lib to `$jetty.home/lib/metro`
4. Edit the start.ini file and add an OPTION line for metro near the end. 4. Edit the start.ini file and add an OPTION line for metro near the end.
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
OPTIONS=metro OPTIONS=metro
---- ----
@ -41,12 +41,12 @@ The Metro distribution you downloaded should also contain several example web ap
Here's an example of the log output from Jetty when one of the sample Metro wars (from `$metro.home/samples/async`) is deployed to Jetty: Here's an example of the log output from Jetty when one of the sample Metro wars (from `$metro.home/samples/async`) is deployed to Jetty:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
[2093] java -jar start.jar [2093] java -jar start.jar
2013-07-26 15:47:53.480:INFO:oejs.Server:main: jetty-9.0.4.v20130625 2013-07-26 15:47:53.480:INFO:oejs.Server:main: jetty-9.0.4.v20130625
2013-07-26 15:47:53.549:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/jetty-distribution-@project.version@/webapps/] at interval 1 2013-07-26 15:47:53.549:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/user/jetty-distribution-{VERSION}/webapps/] at interval 1
Jul 26, 2013 3:47:53 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized Jul 26, 2013 3:47:53 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing INFO: WSSERVLET12: JAX-WS context listener initializing
Jul 26, 2013 3:47:56 PM com.sun.xml.ws.server.MonitorBase createRoot Jul 26, 2013 3:47:56 PM com.sun.xml.ws.server.MonitorBase createRoot

58
jetty-documentation/src/main/asciidoc/development/frameworks/osgi.adoc
View File

@ -98,7 +98,7 @@ jetty.home::
`etc/` directory containing xml files to configure the Jetty container `etc/` directory containing xml files to configure the Jetty container
on startup. For example: on startup. For example:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
jetty.home=/opt/custom/jetty jetty.home=/opt/custom/jetty
@ -106,7 +106,7 @@ jetty.home=/opt/custom/jetty
+ +
Where `/opt/custom/jetty` contains: Where `/opt/custom/jetty` contains:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
etc/jetty.xml etc/jetty.xml
@ -126,7 +126,7 @@ jetty.home.bundle::
jettyhome/` directory with a default set of xml jettyhome/` directory with a default set of xml
configuration files. Here's how you would specify it: configuration files. Here's how you would specify it:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
jetty.home.bundle=org.eclipse.jetty.osgi.boot jetty.home.bundle=org.eclipse.jetty.osgi.boot
---- ----
@ -134,7 +134,7 @@ jetty.home.bundle=org.eclipse.jetty.osgi.boot
Here's a partial listing of that jar that shows you the names of the Here's a partial listing of that jar that shows you the names of the
xml files contained within it: xml files contained within it:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
META-INF/MANIFEST.MF META-INF/MANIFEST.MF
jettyhome/etc/jetty.xml jettyhome/etc/jetty.xml
@ -145,7 +145,7 @@ jetty.etc.config.urls::
This specifies the paths of the xml files that are to be used. If not This specifies the paths of the xml files that are to be used. If not
specified, they default to: specified, they default to:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
etc/jetty.xml,etc/jetty-http.xml,etc/jetty-deployer.xml etc/jetty.xml,etc/jetty-http.xml,etc/jetty-deployer.xml
---- ----
@ -178,7 +178,7 @@ applied to it, and then published as an OSGi service. Normally, you will
not need to interact with this service instance, however you can not need to interact with this service instance, however you can
retrieve a reference to it using the usual OSGi API: retrieve a reference to it using the usual OSGi API:
[source,java] [source, java, subs="{sub-order}"]
---- ----
org.osgi.framework.BundleContext bc; org.osgi.framework.BundleContext bc;
@ -217,7 +217,7 @@ Here's an example of how to create a new Server instance and register it
with OSGi so that the jetty-osgi-boot code will find it and configure it with OSGi so that the jetty-osgi-boot code will find it and configure it
so it can be a deployment target: so it can be a deployment target:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public class Activator implements BundleActivator public class Activator implements BundleActivator
{ {
@ -246,7 +246,7 @@ webapps and ContextHandlers as Bundles or Services to it (see below for
more information on this). Here's an example of deploying a webapp as a more information on this). Here's an example of deploying a webapp as a
Service and targetting it to the "fooServer" Server we created above: Service and targetting it to the "fooServer" Server we created above:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public class Activator implements BundleActivator public class Activator implements BundleActivator
{ {
@ -286,7 +286,7 @@ jetty-9.3) or Jetty-WarResourcePath::
+ +
`MANIFEST`: `MANIFEST`:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Bundle-Name: Web Bundle-Name: Web
@ -300,7 +300,7 @@ Bundle-SymbolicName: com.acme.sample.web
+ +
Bundle contents: Bundle contents:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
META-INF/MANIFEST.MF META-INF/MANIFEST.MF
@ -323,7 +323,7 @@ Bundle MANIFEST contains Web-ContextPath::
+ +
`MANIFEST`: `MANIFEST`:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Bundle-Name: Web Bundle-Name: Web
@ -389,14 +389,14 @@ any file extensions.
For example, suppose we have a bundle whose location is: For example, suppose we have a bundle whose location is:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
file://some/where/over/the/rainbow/oz.war file://some/where/over/the/rainbow/oz.war
---- ----
The corresponding synthesized context path would be: The corresponding synthesized context path would be:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
/oz /oz
---- ----
@ -409,7 +409,7 @@ file that is applied to the webapp. This xml file must be placed in
Here's an example of a webapp bundle listing containing such a file: Here's an example of a webapp bundle listing containing such a file:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
META-INF/MANIFEST.MF META-INF/MANIFEST.MF
@ -469,28 +469,28 @@ Bundle MANIFEST contains Jetty-ContextFilePath::
+ +
A context file that is inside the bundle: A context file that is inside the bundle:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Jetty-ContextFilePath: ./a/b/c/d/foo.xml Jetty-ContextFilePath: ./a/b/c/d/foo.xml
---- ----
+ +
A context file that is on the file system: A context file that is on the file system:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Jetty-ContextFilePath: /opt/app/contexts/foo.xml Jetty-ContextFilePath: /opt/app/contexts/foo.xml
---- ----
+ +
A context file that is relative to jetty.home: A context file that is relative to jetty.home:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Jetty-ContextFilePath: contexts/foo.xml Jetty-ContextFilePath: contexts/foo.xml
---- ----
+ +
A number of different context files: A number of different context files:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Jetty-ContextFilePath: ./a/b/c/d/foo.xml,/opt/app/contexts/foo.xml,contexts/foo.xml Jetty-ContextFilePath: ./a/b/c/d/foo.xml,/opt/app/contexts/foo.xml,contexts/foo.xml
---- ----
@ -529,7 +529,7 @@ bundle.root::
Here's an example of a context xml file that makes use of these Here's an example of a context xml file that makes use of these
properties: properties:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-osgi/test-jetty-osgi-context/src/main/context/acme.xml[] include::{SRCDIR}/jetty-osgi/test-jetty-osgi-context/src/main/context/acme.xml[]
---- ----
@ -550,7 +550,7 @@ WebAppContext:
The bundle contents: The bundle contents:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
META-INF/MANIFEST.MF META-INF/MANIFEST.MF
@ -562,7 +562,7 @@ com/acme/osgi/Activator.class
The `MANIFEST.MF`: The `MANIFEST.MF`:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Bundle-Classpath: . Bundle-Classpath: .
@ -585,7 +585,7 @@ Bundle-SymbolicName: com.acme.testwebapp
The Activator code: The Activator code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public void start(BundleContext context) throws Exception public void start(BundleContext context) throws Exception
@ -659,7 +659,7 @@ apply upon deployment:
The bundle contents: The bundle contents:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
META-INF/MANIFEST.MF META-INF/MANIFEST.MF
@ -673,7 +673,7 @@ com/acme/osgi/Activator$1.class
The `MANIFEST`: The `MANIFEST`:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Bundle-Classpath: . Bundle-Classpath: .
@ -697,7 +697,7 @@ Bundle-SymbolicName: com.acme.testcontext
The Activator code: The Activator code:
[source,java] [source, java, subs="{sub-order}"]
---- ----
public void start(final BundleContext context) throws Exception public void start(final BundleContext context) throws Exception
@ -729,7 +729,7 @@ public void start(final BundleContext context) throws Exception
The contents of the `acme.xml` context file: The contents of the `acme.xml` context file:
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
include::{SRCDIR}/jetty-osgi/test-jetty-osgi-context/src/main/context/acme.xml[] include::{SRCDIR}/jetty-osgi/test-jetty-osgi-context/src/main/context/acme.xml[]
---- ----
@ -939,7 +939,7 @@ Firstly, lets look at an example of a web bundle's modified MANIFEST
file so you get an idea of what is required. This example is a web file so you get an idea of what is required. This example is a web
bundle that uses the Spring servlet framework: bundle that uses the Spring servlet framework:
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
Bundle-SymbolicName: com.acme.sample Bundle-SymbolicName: com.acme.sample
@ -982,7 +982,7 @@ org.eclipse.jetty.osgi.tldbundles::
will be treated as if they are on the container's classpath for web will be treated as if they are on the container's classpath for web
bundles. For example: bundles. For example:
+ +
[source,plain] [source, plain, subs="{sub-order}"]
---- ----
org.eclipse.jetty.osgi.tldbundles=com.acme.special.tags,com.foo.web,org.bar.web.framework org.eclipse.jetty.osgi.tldbundles=com.acme.special.tags,com.foo.web,org.bar.web.framework
---- ----
@ -1012,7 +1012,7 @@ org.eclipse.jetty.server.webapp.containerIncludeBundlePattern::
jetty-deploy.xml file would look if we defined a pattern that matched jetty-deploy.xml file would look if we defined a pattern that matched
all bundle symbolic names ending in "tag" and "web": all bundle symbolic names ending in "tag" and "web":
+ +
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0"?> <?xml version="1.0"?>

4
jetty-documentation/src/main/asciidoc/development/frameworks/spring-usage.adoc
View File

@ -26,7 +26,7 @@ If you want to replace the jetty-xml being used to start the normal Jetty distri
The skeleton of a jetty spring module can be enabled from the jetty-distribution via the link:#startup-modules[module mechanism]. The skeleton of a jetty spring module can be enabled from the jetty-distribution via the link:#startup-modules[module mechanism].
For example: For example:
[source, screen] [source, screen, subs="{sub-order}"]
.... ....
$ java -jar start.jar --add-to-startd=spring $ java -jar start.jar --add-to-startd=spring
.... ....
@ -40,7 +40,7 @@ You will need to download these and place them into jetty's classpath - you can
Configuring Jetty via Spring is simply a matter of calling the API as Spring beans. Configuring Jetty via Spring is simply a matter of calling the API as Spring beans.
The following is an example mimicking the default jetty startup configuration. The following is an example mimicking the default jetty startup configuration.
[source,xml] [source, xml, subs="{sub-order}"]
---- ----
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>

Some files were not shown because too many files have changed in this diff Show More