Jetty in JBoss
The following are required to build and run Jetty in JBoss:
- Java 1.4
- Maven 2.0.4
- JBoss 4.0.5 (other versions may work but this is the version Jetty used for testing)
- JBoss-Jetty module in Jetty 6 - http://svn.codehaus.org/jetty/jetty/trunk/extras/jboss
After checking out the Jetty JBoss module, go to the command line and cd to its home directory. Run:
where path-to-jboss is the location of your JBoss installation. Be sure to specify this directory because maven will use this to obtain the JBoss dependencies.
Building against a different version of JBoss
If you'd like to try rebuilding the Jetty-JBoss integration with a different version of JBoss, do:
where path-to-jboss is the location of your JBoss installation and jboss-version is the version number of your JBoss installation.
If you want to save yourself some typing, an alternate way to build it is to edit the
pom.xml. Edit the <properties> section and fill in the values for the <jboss.home> and <jboss.version> properties. Once these are set in the
pom.xml, you can do the build with:
$JBOSS-HOME/server/default/deploy/jbossweb-tomcat55.sar(or from whichever deploy directory you are using)
- ensure you have built the Jetty JBoss module in $jetty.home/extras/jboss
- copy the $jetty.home/extras/jboss/target/jetty-JETTY-VERSION-jboss-JBOSS-VERSION.sar to your JBoss deploy directory (where JETTY-VERSION is the version of jetty you are using and JBOSS-VERSION is the version of JBoss).
By default, Jetty will be configured to:
- have a thread pool containing a minimum of 10 and a maximum of 250 threads
- a SelectChannelConnector on port 8080
This configuration is contained in the
META-INF/jboss-service.xml file inside the sar.
In order to change the port, add other types of connectors- SSL, AJP13 - configure a request log, or change the thread pool, you need to un-pack the sar to a temporary directory, edit the
META-INF/jboss-service.xml file, repack it and copy the modified sar to the JBoss deploy directory.