NonStop Servlets for JavaServer Pages (5.0) System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
3-11
web.xml
Reloading Servlets
If the reloadable attribute is set to true in the <context>.xml file (located in the
Context configuration file in the $NSJSP_HOME/conf/NSJSP/<host-name>
directory, as shown in Example 3-6), the container automatically reloads classes
(loaded from either the WEB-INF /classes directory or JAR files in the WEB-INF/lib
directory) that have changed.
Note that automatic reload support is not recommended for production applications
because of the extra overhead required to perform the necessary checks on every
request.
Log Files
The iTP_server.xml file also sets the location of the files that contain logging
information. See Section 6, Logs and Error Conditions for details.
web.xml
The web.xml file is a deployment descriptor containing context configuration. A
default version of the web.xml file is located in the $NSJSP_HOME/conf directory.
This file sets the behaviors of all applications and their related resources.
You can also create a version of the same web.xml file within the WEB-INF
subdirectory of any specific application to override the global web.xml file to support
specific servlet control.
The Default Version
The web.xml file in $NSJSP_HOME/conf provides the default path contexts and
controls of servlets and JSP. The text below describes some sample XML control
elements.
Preloading Servlets
A set of servlets can be automatically loaded on startup time by using the <load-on-
startup> element in the web.xml file, as shown in Example 3-7.
The load-on-startup element indicates that this servlet should be loaded on the
startup of the web application. The content of this element must be a positive integer
indicating the order in which the servlets should be loaded. Lower integers are loaded
before higher integers. If no value is specified, or if the value specified is not a positive
integer, the container loads the element any time in the startup sequence.
Example 3-6. Setting the Reloadable Attribute
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" >
</Context>