JSP to HTML compiler
Original Publication Date: 2002-Feb-01
Included in the Prior Art Database: 2003-Jun-20
AbstractA processor is disclosed that allows a Java* Server Page (JSP), populated with example data in special comment blocks, to produce a Hyper Text Markup Language (HTML) output stream populated with the example data.
JSP to HTML compiler
A processor is disclosed that allows a Java* Server Page (JSP), populated with example data in special comment blocks, to produce a Hyper Text Markup Language (HTML) output stream populated with the example data.
For the purpose of this disclosure, a JSP document is defined as a modified HTML document with delimited code embedded in it. The code is run to provide dynamic text that is combined in place with the static text. Usually, a servlet performs business logic, accumulates dynamic data, and passes the data to the JSP for display. See the JSP product page  for complete details.
There are typically 3 steps in developing a JSP.
1. Graphic artists lay out a static HTML page with sample data.
2. Developers replace the sample data with delimited code that produce data dynamically.
3. Developers/testers construct a test environment that will exercise the JSP code.
The problem with the above method is that it assumes a waterfall methodology. It assumes layout will be done first, and then coding and testing, and that no further layout rework is required. It also assumes that a test environment will be readily available.
It is typical that once the HTML page has been converted to a JSP, a layout change is required and that the artist has to go back and change the look of the page based on customer feedback. The artist now has two choices:
1) Change and test the page outside of a test environment.
2) Change and test the page inside of a test environment. Each choice has disadvantages. Choice 1) means that the page will not render correctly as the dynamic code will not run. Choice
2) allows the artist to see the effects of his changes with sample data, but requires the artist to be technically inclined or have a support staff. It also requires connectivity to the test environment.
The disclosed technique uses a processor and example data embedded in special comments marked by a trigger word. A schedule of trigger words is listed in schedule 1. The processor combines the static HTML text with the example data following the trigger to produce a HTML output stream that can be viewed by the artist to test his changes. This technique may also be useful for documentation teams to pro...