Scribd
Upload
74 views

Understanding JSP Life Cycle

The JSP life cycle consists of four phases: translation, initialization, execution, and finalization. In the translation phase, the JSP engine checks the JSP syntax and translates the JSP page into a Java servlet class. In initialization, an instance of the servlet is created to handle requests. In execution, the _jspService() method handles each request and returns a response. In finalization, the jspDestroy() method cleans up memory and resources.

Uploaded by

subhjitbsp49
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
74 views

Understanding JSP Life Cycle

The JSP life cycle consists of four phases: translation, initialization, execution, and finalization. In the translation phase, the JSP engine checks the JSP syntax and translates the JSP page into a Java servlet class. In initialization, an instance of the servlet is created to handle requests. In execution, the _jspService() method handles each request and returns a response. In finalization, the jspDestroy() method cleans up memory and resources.

Uploaded by

subhjitbsp49
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Understanding JSP Life Cycle

JSP never outputs the content directly to the browser. Instead, JSP replies on initial server-
side processing process which translates JSP page into the JSP Page class. The page class then will handle all the
requests made of JSP. The JSP life cycle is described as the picture below:

JSP Life Cycle


JSP life cycle can be divided into four phases: Translation, Initialization, execution and finalization.
Translation
In the translation phase, JSP engine checks for the JSP syntax and translate JSP page into its page implementation
class if the syntax is correct. This class is actually a standard Java servlet. After that, JSP engine compiles the source
file into class file and ready for use.
If the container receives the request, it checks for the changes of the JSP page since it was last translated. If no
changes was made, It just loads the servlet otherwise the process of check, translate and compile occurs again.
Because the compilation process takes time so JSP engine wants to minimize it to increase the performance of the
page processing.
Initialization
After the translation phase, JSP engine loads the class file and create an instance of of the servlet to
handle processing of the initial request. JSP engines will call a method jspInit() to initialize the a servlet. jspInit
method is generated during the translation phase which is normally used for initializing application-level parameters
and resources. You can also overide this method by using declaration.
<%!
public void jspInit(){
// put your custom code here
}
%>
Execution
After the initialization phase, the web container calls the method _jspService() to handle the request and returning a
response to the client. Each request is handled is a separated thread. Be noted that all the scriptlets and expressions
end up inside this method. The JSP directives and declaration are applied to the entire page so the are outside of this
method.
Finalization
In the finalization phase, the web container calls the method jspDestroy(). This method is used to clean up memory
and resources. Like jspInit() method, you can override the jspDestroy()method also to do your all clean up such as
release the resources you loaded in the initialization phase....
<%!
public void jspDestroy(){
// put your custom code here
// to clean up resources
}
%>

You might also like