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

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005
3-78
The web.xml File
Default Servlet
As the name implies, it is generally configured as the default servlet for a web
application, by being mapped to the URL pattern /. For more information, see
http://tomcat.apache.org/tomcat-7.0-doc/funcspecs/fs-default.html.
Example 3-52
shows the configuration of the default Servlet.
Invoker Servlet
The invoker servlet is not supported starting NSJSP 7.0 release.
JSP Page Compiler and Execution Servlet
The JSP Page Compiler and Execution Servlet is the mechanism used by NSJSP
(inherited from Tomcat) to process JSP pages. Traditionally, this servlet is mapped to
the URL pattern *.jsp. You can use the default configuration for most applications.
MaxLoadedJsps
For more information on the JSP Page Compiler and Execution Servlet, see
http://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html
Example 3-52. Configuration of the Default Servlet
<servlet>
<servlet-name>default</servlet-name>
<servlet-
class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>listings</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
.
.
.
<!-- The mapping for the default servlet -->
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
Note. HP recommends that the Invoker Servlet not be used, because it could lead to
security issues. For example, enabling the invoker servlet allows a URL to directly invoke
the servlet using its class path, thereby bypassing all the security constraints defined in the
web application deployment descriptor.