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

Migrating to NSJSP 7.0
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005
7-16
Container-Specific Resources
HP recommends that all application-specific resources be bundled with the application
and not be placed in the shared folder. This is to ensure that the application resources
are independent of the container.
Container-Specific Resources
The <NSJSP_HOME>/lib folder includes the common and the container-specific
libraries. Although NSJSP 7.0 introduces a few more libraries , they are used internally
by the container.
Compiling the Application
NSJSP7.0 implements the Java Servlets 3.0 specification. You need to check if your
application is compliant with 3.0 specification. This can be done by compiling your
application with the servlet-api.jar and jsp-api.jar both located in
<NSJSP_HOME>/lib.
Session Store
The functionality of session store in NSJSP 7.0 is the same as that of NSJSP 6.1.
However, you can reuse the session store of NSJSP 6.1 as is for NSJSP 7.0.
Deploying Web Applications in NSJSP 7.0
The deploying web applications work the same in NSJSP 7.0 as it did in NSJSP 6.1.
However, a new attribute copyXML is introduced and set to false by default. For
more information on context.xml, see The context.xml File on page 3-69.
Application Deployed Using a context.xml File
If an application is deployed using its context definition file, HP recommends that you
deploy the application using the NSJSP Manager. An application is deployed using the
context.xml, as follows:
The path attribute of the context element in the context definition is ignored. The path
is derived from the name of the context definition file. For example, if the name of the
context definition file is foo.xml, the path of the context is /foo.
The NSJSP Manager provides an option to deploy an application using its context
definition file. In this case, you can mention the context path and the manager derives
the name of the context definition file from the path specified. For example, if the value
of path is /foo and the full path to context definition file is
/usr/webmstr/webapps/myapp.xml, the NSJSP Manager copies the myapp.xml
file to the appropriate location in NSJSP 7.0 with the name foo.xml and then deploys
the application based on the contents of foo.xml.