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

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
3-67
The web.xml File
Example 3-53 shows the configuration of the default Servlet.
Invoker Servlet
The invoker servlet allows a web application to dynamically register new servlet
definitions, without having created a new <servlet> element in the /WEB-
INF/web.xml deployment descriptor, and execute requests utilizing the new servlet
definitions. From the perspective of the newly registered servlets, all servlet lifecycle
requirements of the Servlet Specification (such as calling init() and destroy() at
the correct times) are honoured. For more information, see
http://tomcat.apache.org/tomcat-6.0-doc/funcspecs/fs-invoker.html
. The Invoker
Servlet and the servlet-mapping for the Invoker Servlet are commented out. For
more information on the Invoker Servlet, see The
Region Directive on page 3-28.
Example 3-54
shows the configuration of the invoker servlet.
Example 3-53. 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.