iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using NonStop Servlets for JavaServer Pages
(NSJSP)
iTP Secure WebServer System Administrator’s Guide—523346-002
9-35
International Character Set Support
Secure WebServer environment tends to limit, but does not rule out, breaches of
security. Specifically, neither the iTP Secure WebServer nor the NSJSP places any
restrictions on what a servlet does, beyond restrictions imposed by NonStop Server for
Java.
The web container inherits the security attributes of the PATHMON environment.
International Character Set Support
The iTP Secure WebServer supports international character sets (Unicode) for input to
and output from the Servlet environment. No specific configuration procedures are
required to use international character sets with servlets in the iTP Secure WebServer
environment.
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
This is an overview of the main features of JavaServer Pages and discusses the
reasons for using distributed servlets, how to include one servlet in another, or forward
responses between servlets. Simple examples of JSP code are annotated.
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 Java website, 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.