Scribd
Upload
9 views

8jsp Implicit Objects

The document discusses the 9 implicit objects available in JSP pages. These include request, response, out, session, application, config, pageContext, page, and exception. Each implicit object provides access to important information and functionality. For example, request and response allow accessing HTTP headers and client data, out writes to the output stream, and session supports client session tracking across requests.

Uploaded by

Amali Xavier
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

8jsp Implicit Objects

The document discusses the 9 implicit objects available in JSP pages. These include request, response, out, session, application, config, pageContext, page, and exception. Each implicit object provides access to important information and functionality. For example, request and response allow accessing HTTP headers and client data, out writes to the output stream, and session supports client session tracking across requests.

Uploaded by

Amali Xavier
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

JSP - IMPLICIT OBJECTS

http://www.tuto rialspo int.co m/jsp/jsp_implicit_o bje cts.htm Co pyrig ht © tuto rials po int.co m

JSP Implicit Objects are the Java objects that the JSP Container makes available to developers in each pag e and
developer can call them directly without being explicitly declared. JSP Implicit Objects are also called pre-
defined variables.

JSP supports nine Implicit Objects which are listed below:

O bjec t Desc ription

request T his is the HttpServletRequest object associated with the request.

response T his is the HttpServletResponse object associated with the response


to the client.

out T his is the PrintWriter object used to send output to the client.

session T his is the HttpSession object associated with the request.

application T his is the ServletContext object associated with application context.

config T his is the ServletConfig object associated with the pag e.

pag eContext T his encapsulates use of server-specific features like hig her performance
J spWriters.

pag e T his is simply a synonym for this, and is used to call the methods defined by
the translated servlet class.

Exception T he Exc eption object allows the exception data to be accessed by


desig nated JSP.

The request Object:


T he request object is an instance of a javax.servlet.http.HttpServletRequest object. Each time a client requests
a pag e the JSP eng ine creates a new object to represent that request.

T he request object provides methods to g et HT T P header information including form data, cookies, HT T P
methods etc.

We would see complete set of methods associated with request object in coming chapter: JSP - Client Request.

The response Object:


T he response object is an instance of a javax.servlet.http.HttpServletResponse object. Just as the server
creates the request object, it also creates an object to represent the response to the client.

T he response object also defines the interfaces that deal with creating new HT T P headers. T hroug h this object
the JSP prog rammer can add new cookies or date stamps, HT T P status codes etc.

We would see complete set of methods associated with response object in coming chapter: JSP - Server
Response.

The out Object:


T he out implicit object is an instance of a javax.servlet.jsp.JspWriter object and is used to send content in a
response.

T he initial JspWriter object is instantiated differently depending on whether the pag e is buffered or not.
Buffering can be easily turned off by using the buffered='false' attribute of the pag e directive.

T he JspWriter object contains most of the same methods as the java.io.PrintWriter class. However, JspWriter
has some additional methods desig ned to deal with buffering . Unlike the PrintWriter object, JspWriter throws
IOExceptions.

Following are the important methods which we would use to write boolean char, int, double, object, String etc.

Method Desc ription

out.print(dataT ype dt) Print a data type value

out.println(dataT ype dt) Print a data type value then terminate the line with new line
character.

out.flush() Flush the stream.

The session Object:


T he session object is an instance of javax.servlet.http.HttpSession and behaves exactly the same way that
session objects behave under Java Servlets.

T he session object is used to track client session between client requests. We would see complete usag e of
session object in coming chapter: JSP - Session T racking .

The application Object:


T he application object is direct wrapper around the ServletContext object for the g enerated Servlet and in
reality an instance of a javax.servlet.ServletContext object.

T his object is a representation of the JSP pag e throug h its entire lifecycle. T his object is created when the JSP
pag e is initialized and will be removed when the JSP pag e is removed by the jspDestroy() method.

By adding an attribute to application, you can ensure that all JSP files that make up your web application have
access to it.

You can check a simple use of Application Object in chapter: JSP - Hits Counter

The config Object:


T he config object is an instantiation of javax.servlet.ServletConfig and is a direct wrapper around the
ServletConfig object for the g enerated servlet.

T his object allows the JSP prog rammer access to the Servlet or JSP eng ine initialization parameters such as the
paths or file locations etc.

T he following config method is the only one you mig ht ever use, and its usag e is trivial:

config.getServletName();

T his returns the servlet name, which is the string contained in the <servlet-name> element defined in the WEB-
INF\web.xml file

The pag eContext Object:


T he pag eContext object is an instance of a javax.servlet.jsp.Pag eContext object. T he pag eContext object is
used to represent the entire JSP pag e.

T his object is intended as a means to access information about the pag e while avoiding most of the
implementation details.
T his object stores references to the request and response objects for each request. T he application, config ,
session, and out objects are derived by accessing attributes of this object.

T he pag eContext object also contains information about the directives issued to the JSP pag e, including the
buffering information, the errorPag eURL, and pag e scope.

T he Pag eContext class defines several fields, including PAGE_SCOPE, REQUEST _SCOPE,
SESSION_SCOPE, and APPLICAT ION_SCOPE, which identify the four scopes. It also supports more than 40
methods, about half of which are inherited from the javax.servlet.jsp. JspContext class.

One of the important methods is removeAttribute, which accepts either one or two arg uments. For example,
pag eContext.removeAttribute ("attrName") removes the attribute from all scopes, while the following code only
removes it from the pag e scope:

pageContext.removeAttribute("attrName", PAGE_SCOPE);

You can check a very g ood usag e of pag eContext in coming chapter: JSP - File Uploading .

The pag e Object:


T his object is an actual reference to the instance of the pag e. It can be thoug ht of as an object that represents the
entire JSP pag e.

T he pag e object is really a direct synonym for the this object.

The exception Object:


T he exception object is a wrapper containing the exception thrown from the previous pag e. It is typically used to
g enerate an appropriate response to the error condition.

We would see complete usag e of this object in coming chapter: JSP - Exception Handling .

You might also like