|
How it works
Assume you build a JSP page in UltraDev and upload it to your remote site (which should be a JRun application root folder).
The first time the JSP page is requested by a browser, the Web server hands it off to JRun, which performs the following tasks:
| 1 |
It converts the page's contents—including all HTML code—into Java source code. |
|
Static HTML is translated into Java strings to be converted back to HTML later; JSP code is translated into Java code for generating dynamic content. |
| 2 |
It compiles the source code into a Java servlet. |
| 3 |
It places both the source file (.java) and the servlet (.class) in the WEB-INF\jsp folder in the JRun application root folder. |
| 4 |
It runs the servlet to generate an HTML page in response to the page request. |
 |
|
Like a CGI script, the servlet generates a pure HTML document and hands it off to the Web server to be passed on to the requesting browser.
The second time a JSP page is requested, JRun finds out whether or not you revised the JSP page since the servlet was last compiled. To do so, it compares the date stamps on the JSP file and the servlet file. If the date stamp on the JSP is more recent than the servlet's, JRun knows you revised the JSP page since it was compiled, and compiles a new one incorporating your changes. Otherwise, JRun simply runs the existing servlet.
|
