iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using NonStop Servlets for JavaServer Pages
(NSJSP)
iTP Secure WebServer System Administrator’s Guide—523346-002
9-22
web.xml
Note that automatic reload support is not recommended for production applications
because of extra overhead required to perform the necessary checks on every request.
For example:
<Context path="/examples" docBase="webapps/examples"
debug="0"reloadable="true" >
</Context>
Log Files
The file also sets the location of the files that contain logs of low-level events. See
Logs and Error Conditions on page 9-41 for details.
web.xml
The web.xml file is known as a deployment descriptor. It contains configuration
contexts for a web application. A default version of web.xml is located in
servlet_jsp/conf. This sets the behaviors of all applications and their related
resources.
There is also a version of the same file that you can create within the WEB-INF
subdirectory of any specific application, which overrides the "global" web.xml file and
thus support specific servlet control.
The Default Version
The web.xml file in /usr/tandem/webserver/servlet_jsp/conf provides the
default path contexts and controls of servlets and JSP. Here are some example 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.
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 is free to load it any time in the startup sequence.