NonStop Servlets for JavaServer Pages (5.0) System Administrator's Guide
Migrating to NSJSP 5.0
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
7-5
Strict Rules on TagExtraInfo Classes
If the Invoker Servlet is disabled, some servlets in your web applications might not 
work and may return error 404 (page not found) to the browser. This problem occurs if 
your web application descriptors do not explicitly describe all of the servlet mappings.
Example 7-1 illustrates how to add mappings for a servlet to a web application's 
deployment descriptor (web.xml file).
Strict Rules on TagExtraInfo Classes
With the implementation of the JSP 2.0 specification, any TagExtraInfo Classes 
defined in a web application's TLD (TagLibrary Descriptor) files through <teiclass> 
tag must be present even if they are not referenced. An Error 500 (server error) may 
be returned to the browser if any such defined TagExtraInfo class cannot be found in 
the CLASSPATH (even if the specific custom tag is not used). In prior releases, an 
exception was thrown only when the specific custom tag was referenced.
Persistent Sessions Database Changes
For NSJSP 5.0, the persistent session database has an additional column, app_name, 
for specifying the associated application. Below is the new iTP_SessionStore.sql 
script for creating the session database.
create table =TheT1222SessionCatalog.SessData (
 session_id VARCHAR(48) NO DEFAULT NOT NULL,
 process_name VARCHAR(8) NO DEFAULT NOT NULL,
 rec_number INTEGER UNSIGNED NO DEFAULT NOT NULL,
 app_name VARCHAR(255) NO DEFAULT NOT NULL,
 session_data VARCHAR(3712) CHARACTER SET ISO88591, 
 valid SMALLINT UNSIGNED NO DEFAULT,
 maxinactiveinterval INTEGER NO DEFAULT,
 lastaccessedLARGEINT NO DEFAULT,
 primary key (session_id, process_name, rec_number) )
For existing NSJSP persistent session database, a new shell script 
nsjsp_migrateSessionStore is provided to ease the migration. The script alters 
your exising table for the additional column. 
The example above assumes that you are creating a NonStop SQL/MP database 
table. If you wish to create a NonStop SQL/MX database table, please be aware that 
the maximum record size limit is 4036 bytes (unlike the 4096 byte limit in SQL/MP). As 
Example 7-1. Mapping Servlets in the Web Application Deployment Descriptor 
(web.xml) 
<servlet>
 <servlet-name>start</servlet-name>
 <servlet-class>startCartRequest</servlet-class>
</servlet>
<servlet-mapping>
 <servlet-name>start</servlet-name>
 <url-pattern>/servlet/startCartRequest</url-pattern>
</servlet-mapping>










