JSP operation insider

Author: Zhao Branch from: open systems world

Regular friends ask, what is the difference between JSP and Servlet? What is the connection between the two? In fact, the performance of servlet technology is very early, which is developed for the application of Java server. Everyone knows that applet is a applet, servlet is a server-side applet. However, after Microsoft's ASP technology appears, the output statement of a row of rows when using the servlet, is very awkward, and this is the case for complex layout or display pages. JSP is to meet this need to be developed on servlet technology. It can be seen that there is an intrinsic blood relationship between JSP and Servlet. When learning JSP, if you can seize this connection, you can understand the operational mechanism of JSP and achieve the effect of halving. This article will pass the inside of JSP operation through the analysis of a JSP operation process, and the technical points in some JSPs are set forth from a new perspective.   helloworld.jsp   We take Tomcat 4.1.17 servers as an example to see how the simplest helloWorld.jsp runs. Code List 1: HelloWorld.jsp

HelloWorld.jsp

<%

String message = "Hello World!";

%>

<% = message%>

This file is very simple, only defines a string variable and outputs. Put this file in the Tomcat's WebApps / root / directory, start Tomcat, access http: // localhost: 8080 / helloworld.jsp, the output in the browser is "HelloWorld!"

Let us see what Tomcat has done. Go to Tomcat / Work / Standalone / localhost / _ directory, you can find the following helloworld_jsp.java, this file is the source file generated when Tomcat parsing HelloWorld.jsp:

Code List 2: HelloWorld_Jsp.Java

Package org.apache.jsp;

Import javax.servlet. *;

Import javax.servlet.http. *;

Import javax.servlet.jsp. *;

Import org.apache.jasper.runtime. *;

Public class helloworld_jsp extends httpjspbase {

......

Public void _jspservice (httpservletRequest Request,

Httpservletresponse response) throws java.io.ioException, servletexception

{

JSPFactory _jspxfactory = null;

Javax.servlet.jsp.pageContext pageContext = null;

HttpSession session = null;

ServletContext Application = NULL;

ServletConfig CONFIG = NULL;

Jspwriter out = NULL;

Object Page = THIS;

JSPWriter_Jspx_out = NULL;

Try {

_jspxfactory = jspfactory.getDefaultFactory ();

Response.setContentType ("Text / HTML; Charset = ISO-8859-1); PageContext = _jspxFactory.getPageContext (this, Request, Response, Null, True, 8192, True);

Application = pageContext.getServletContext ();

CONFIG = pageContext.getServletConfig ();

Session = pageContext.getsession ();

OUT = PageContext.getut ();

_Jspx_out = OUT;

String message = "Hello World!";

OUT.PRINT (Message);

} catch (throwable t) {

OUT = _jspx_out;

IF (out! = null && out.getBuffersize ()! = 0)

Out.clearbuffer ();

IF (pageContext! = null) PageContext.HandlepageException (T);

} finally {

IF (_jspxfactory! = null) _jspxfactory.releasePageContext (PageContext);

}

}

}

As can be seen from the above, helloWorld.jsp first parsed to a Java class helloworld_jsp.java, which inherits in the org.apache.jasper.Runtime.httpjspBase base class, HTTPJSPBASE implements the httpservlet interface. It can be seen that JSP first compiled into a servlet before running, which is the key to understanding JSP technology.

We also know that there are several objects in the JSP page, such as PageContext, Application, Config, Page, Session, Out, etc. You may be strange, why you can use these built-in objects directly in the code snippet in the JSP. Observe _JspService () method, in fact, these built-in objects are defined here. Initialize these built-in objects before analyzing the code snippet in the JSP file.

First, call the JSPFactory's getDefaultFactory () method to obtain a reference to a JSPFactory object of the container implementation (refer to Tomcat 4.1.17). JSPFactory is an abstract class defined in the javax.servlet.jsp package, which defines two static methods set / getDefaultFactory (). The SET method is placed by the JSP container (Tomcat). When the page servlet (ie HelloWorld_JSP class) is placed, it can directly call the JSPFactory.getDefaultFactory () method to get the implementation class of this JSP factory. Tomcat is called org.apache.jasper.Runtime.jspFactoryImpl class.

Then, call this JSPFactoryImpl's getPageContext () method, populate a PageContext, and assign the built-in variable PageConext. Other built-in objects are obtained via this pageContext. The specific process see the code above, and details will not be described here. The page servlet's environment is complete, and the page begins to parse the page. The HelloWorld.JSP page only defines a string variable and then outputs it directly. The parsed code is as follows: Code List 3: JSP page analysis code snippet

String message = "Hello World!";

OUT.PRINT (Message);

Customized tag analysis process

In a large web application, JSP custom labels are usually used to encapsulate page display logic. An analysis of the parsing process of the custom label is very helpful to our in-depth understanding of the operational mechanism of customized labels. Below we run as an example with the homepage of Struts-Example apps attached in Struts1.1.

INDEX.JSP containing custom labels

The download address of Struts1.1 is http://jakarta.apache.org/struts/index.html. Put the downloaded package, you can find Struts-Example.war under the WebApps directory. Copy the WAR package to the Tomcat's WebApps directory, Tomcat will automatically install this package. Access the Struts-Example App to HTTP: // localhost: 8080 / Struts-Example in the browser, the home page of the app is displayed (see Figure 1).

Figure 1 Home

Code List 4: INDEX.JSP

<% @ page contenttype = "text / html; charset = uTF-8" Language = "java"%>

<% @ Taglib Uri = "/ Web-INF / STRUTS-Bean.tld" prefix = "bean"%>

<% @ Taglib URI = "/ Web-INF / STRUTS-HTML.TLD" prefix = "html"%>

<% @ Taglib URI = "/ Web-INF / STRUTS-LOGIC.TLD" prefix = "logic"%>