Jsp Configuration

...

1. Check the jsp files for possible recompilation on every request:

   Code Block
   xml
   <init-param> <param-name>development</param-name> <param-value>true</param-value> </init-param>

2. Only check approximately every N seconds, where a request will trigger the time-lapse calculation. This example checks every 60 seconds:

   Code Block
   xml
   <init-param> <param-name>development</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>modificationTestInterval</param-name> <param-value>60</param-value> </init-param>

3. Do no checking whatsoever, but still compile the jsp on the very first hit. (Note: this "reload-interval" parameter is a short hand for a "development=false" and "checkInterval=0" combination):

   Code Block
   xml
   <init-param> <param-name>reload-interval</param-name> <param-value>-1</param-value> </init-param>

4. Don't do any request-time checking, but instead start a background thread to do checks every N seconds (in the example below, every 60 sec):

   Code Block
   xml
   <init-param> <param-name>development</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>checkInterval</param-name> <param-value>60</param-value> </init-param>

Modifying the Configuration

There are several options for modifying the Jasper JSP servlet configuration.

Override webdefault.xml

You can make a copy of the webdefault.xml shipped with jetty, apply your changes and use it instead of the shipped version. The example below shows
how to do this when using the maven jetty plugin.

 <plugin>
   <groupId>org.mortbay.jetty</groupId>
   <artifactId>jetty-maven-plugin</artifactId>
   <configuration>
   <webAppConfig>
     <defaultsDescriptor>src/main/resources/webdefault.xml</defaultsDescriptor>
   </webAppConfig>
   <connectors>
   ..