Overview of JSP Applications and Sessions

This section provides a brief overview of how JSP applications and sessions are supported by OracleJSP.

General OracleJSP Application and Session Support

OracleJSP uses underlying servlet mechanisms for managing applications and sessions. For information about these mechanisms, see "Servlet Sessions" and "Servlet Contexts". For servlet 2.1 and servlet 2.2 environments, these underlying mechanisms are sufficient, providing a distinct servlet context and session object for each JSP application.

Using the servlet mechanisms becomes problematic, however, in a servlet 2.0 environment such as Apache/JServ. The concept of a Web application was not well defined in the servlet 2.0 specification, so in a servlet 2.0 environment there is only one servlet context per servlet container. Additionally, there is one session object only per servlet container. However, for Apache/JServ and other servlet 2.0 environments, OracleJSP provides extensions to optionally allow distinct servlet contexts and session objects for each application. (This is unnecessary for Web servers hosting just a single application.)

Note: For additional information relevant to Apache/JServ and other servlet 2.0 environments, see "Considerations for Apache/JServ Servlet Environments" and "Overview of globals.jsa Functionality".

JSP Default Session Requests

Generally speaking, servlets do not request an HTTP session by default. However, JSP page implementation classes do request an HTTP session by default. You can override this by setting the session parameter to false in a JSP page directive, as follows:

<%@ page ... session="false" %>

---