iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)
Using NonStop Servlets for JavaServer Pages With 
The iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
9-33
Reserved Cookie Name
Reserved Cookie Name
•
The cookie name "JSESSIONID" is reserved for internal use. According to the 
Servlet API 2.2 the name of the session tracking cookie must be "JSESSIONID" and 
the name of the session tracking parameter used in the URL rewriting must be 
"jsessionid".
JavaServer Pages
A general introduction to JSP is given in JavaServer Pages on page 9-7. This section 
introduces implementation, models and syntax basics. For full details consult Sun 
Microsystems JSP websites, such as java.sun.com.
Typically JSP pages are subject to a translation phase and a request processing phase. 
The translation phase is carried out once (unless the page changes) when the JSP page is 
requested the first time. The result is a JSP page implementation class file that 
implements the Servlet interface. 
The JSP page implementation class file extends HttpJspBase, which in turn implements 
the Servlet interface. The service method of this class, _jspService( ), essentially inlines 
the contents of the JSP page. Although the _jspService cannot be overridden, you can 
effect initialize and destroy events by providing implementations for the jspInit( ) and 
jspDestroy( ) methods within your own pages. When the class file is loaded within the 
web container, the _jspService( ) method is responsible for replying to a client request. 
By default, the _jspService( ) method is dispatched on a separate thread by the web 
container in processing concurrent client requests.
Model-View-Controller Designs
There are two design philosophies for JSP usage. The approaches differ in terms of 
where most of the processing takes place. In the first approach, shown in Figure 9-4, A 
Basic JSP Model, the incoming request from a web browser is sent directly to the JSP 
page which is responsible for processing it and replying back to the client. There is 
separation of content from presentation because data access is performed using Java 
beans.










