W E B   S E R V I C E S  

webapps to be able to reference EJBs , resources and other objects in the J2EE JNDI 

environment. 

Logging 

Debug and informational log output from the Jetty Service is adapted to the standard 

JBoss logging service. 

Security 

The Jetty integration classes adapt the servlet security environment to the JBoss 

securityenvironment. This allows webapps performing basic or form based authentication 

to transparently access the JBossSX framework. 

JMX 

As a compliant JBoss service, Jetty can be controlled from the mbean viewer available on 

port 8082.  Jetty makes available each of its constituent components as mbeans allowing 

detailed management of configuration, debugging and statistics gathering. Additionally, 

Jetty creates an mbean for every deployed web application context, allowing individual 

contexts to be stopped and (re)started without undeploying the webapp itself. 

Clustered Sessions 

The clustered HTTP Session service can be used to provide distributed sessions. 

Deployment 

Jetty is packaged as a service archive file called 

jetty plugin.sar

. It deploys 

automatically with JBoss with a default configuration: 

1.it will listen on port 8080 for HTTP requests (note that as no demonstration webapp is 

provided, hitting 

localhost:8080/

 will result in your receiving a "

404 NotFound

")  

2.the HTTP request log is written to the standard JBoss log directory as files with names of 

the form 

yyyy_mm_dd.request.log

 which rollover daily 

3.output from Jetty such as debug and informational messages are directed to the standard 

JBoss log 

111