I often ask if there is any 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 by analyzing an JSP operation process, and elaborate from a new perspective. HelloWorld.jsp We take Tomcat 4.1.17 servers as an example to see how the simplest helloworld.jsp is running. 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's take a look at Tomcat I did what. Go to Tomcat / Work / Standalone / LocalHost / _Dext, you can find the following helloWorld_jsp.java, this file is the source file generated when Tomcat resolves 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.getOut ( ); _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);} finaryly {= _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: The code snippet after the JSP page is resolved String Message = "Hello World!"; Out.print (Message);
The parsing process of custom labels typically uses JSP custom labels to encapsulate page display logic in a large web application in a large web application. 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. The download address of Index.jsp Struts1.1b containing custom labels 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"%> ... ...
We are only in index.jsp
The parship parsing is an example of analysis, how does the container analyze this custom label into HTML output. The above code omits other display portions of the page. First, look at the source file of the page in the browser above:
......
It can be seen that the container has already put
Replace with a string, the title of the page is displayed.
The analysis process then, how does the JSP container complete parsing? View Index_Jsp.java files after working directory Jakarta-Tomcat-4.1.17 / work / standalone / localhost / struts-example: Code List 5: INDEX_Jsp.JAVA
package org.apache.jsp; import javax.servlet *;. import javax.servlet.http *;. import javax.servlet.jsp *;. import org.apache.jasper.runtime *;. public class index_jsp extends HttpJspBase {/ / private org.apache.jasper.runtime.TagHandlerPool all references to custom label definition of the processor pool; _jspx_tagPool_bean_message_key; ...... // page class constructor public index_jsp () {_jspx_tagPool_bean_message_key = new org.apache.jasper.runtime. TagHandlerPool (); ......} public void _jspService (HttpServletRequest request, HttpServletResponse response) throws java.io.IOException, ServletException {...... _jspxFactory = JspFactory.getDefaultFactory (); response.setContentType ( "text / html; charset = UTF-8 "); pageContext = _jspxFactory.getPageContext (this, request, response, null, true, 8192, true); application = pageContext.getServletContext (); config = pageContext.getServletConfig (); session = pageContext.getSession (); out = PageContext.get (); _jspx_out = out; ... if (_jspx_meth_html_html_0) Return; ...} // Release all custom labels when processing exit PUBLIC VOID _J Spdestroy () {_jspx_tagpool_bean_message_key.release (); ......}} The generated index_jsp.java inherits in org.apache. jasper.Runtime.httpjspBase. Research this document provides us to understand the operational mechanism of custom labels.
As can be seen from the above, Tomcat first defines each custom label and instantizes a TagHandlerPool object for each custom tag when parsing a JSP page. The processing method of the page covers the _ jspservice () method of the parent class, _jspservice method first initializes the environment and assigns a built-in object. Since the index.jsp page is as a whole
The label package, Tomcat generates a private method to each tag.
The processing method of the label is _Jspx_meth_html_html_0 (). The naming specification of this method can also be seen from here, "_jspx_meth tag prefix tag name This tag appears in the JSP page." Other tags are included in the label, so other tags are parsed in the _jspx_meth_html_html_0 () method. For specific code implementations, see Caidi.com http://linux.ccidnet.com Journal Browse 2003 No. 6.
In the _jspx_meth_html_html_0 () method, you first get an instance of org.apache.struts.taglib.html.htmltag from the _jspx_tagpool_html_html_locale pool, then set the page context of this Tag instance, due to the HTML: HTML tag is page The top label, so its Parent is NULL. Then parse the contents of the label. HTML code direct output, the following mainly look at the label
Analysis of the label. Analysis of the Bean: Message Tag is similar to HTML: HTML, Tomcat also puts it in a separate method _jspx_meth_bean_message_0 ().
BEAN: Message Tag List 7: _JSPX_METH_BEAN_MESSAGE_0 () method pieces
// message processing method of custom tags private boolean _jspx_meth_bean_message_0 (javax.servlet.jsp.tagext.Tag _jspx_th_html_html_0, javax.servlet.jsp.PageContext pageContext) throws Throwable {JspWriter out = pageContext.getOut (); / * --- - bean: message ---- * / org.apache.struts.taglib.bean.MessageTag _jspx_th_bean_message_0 = (org.apache.struts.taglib.bean.MessageTag) _jspx_tagPool_bean_message_key.get (org.apache.struts.taglib.bean. MessageTag.class); _jspx_th_bean_message_0.setPageContext (pageContext); _jspx_th_bean_message_0.setParent (_jspx_th_html_html_0); _jspx_th_bean_message_0.setKey ( "index.title"); int _jspx_eval_bean_message_0 = _jspx_th_bean_message_0.doStartTag (); if (_jspx_th_bean_message_0.doEndTag () == javax. servlet.jsp.tagext.tag.skip_page) Return true; _jspx_tagpool_bean_message_key.reuse (_jspx_th_bean_message_0); return false;}
Similarly, the HTML: Bean also needs to get an instance of a label class from the pool, and then set the environment. Not detailed here. We only focus on the special processing section of the MessageTag custom label class. The development of custom labels is not within the scope of this article. Define a bean: Message tag in Index.jsp, and set an attribute:
. When Tomcat is parsed, call the key property setting method setKey () of the MessageTag object, and place the property. Then call MessageTAG's dostartTAG () and doendTag () methods to complete the resolution. If the return value of the DOENDTAG () method is javax.servlet.jsp.tagext.tag. Skip_page, indicating that the resolution is completed, returns true, Tomcat will immediately stop the execution of the remaining page code and return. Otherwise put the instance of the MessageTag back into the pool.
Chihua, a label object instance, in order to improve the running efficiency, Tomcat is done to all custom labels, and the pool is done by org.apache.jasper. Runtime.taghandlerpool class. There are two classes TagHandlerPool as the following code: Code Listing 8: TagHandlerPool.javapublic class TagHandlerPool {private static final int MAX_POOL_SIZE = 5; private Tag [] handlers; public synchronized Tag get (Class handlerClass) throws JspException {......} public Synchronized void reuse (tag handler) {...}}
TagHandlerPool simply implements the pool of tag classes, where max_pool_size is the initial size of the pool, and Handlers is an array of TAGs, instances of the label class. Get (class handlerclass) gets an instance of a specified tag class. If there is no instance in the pool, a new instance is new. Reuse (Tag Handler) puts the Handler object back in the pool. At this point, we have the operation of JSP in the container. Although the resolution of each JSP container will differ, but the principles are similar. For written JSP applications, we do not need to interfere with the running process in the container, but if you are familiar with the overall running mechanism, you can have a deeper understanding of JSP / servlet technology.
