A Java Server Page (JSP) is a dynamic Web page comprised of HTML or XML markup, along with Java code. Each page is automatically compiled into a servlet by the JSP engine and a Java compiler the first time it is requested. The generated and compiled servlet is then executed, and its output is well-formed HTML.
To develop JSP, a java compiler must be available. The Tomcat servlet engine provided with EPX includes the Java compiler jikes.exe on Windows 2003 and Windows 2000.
EPX configures Tomcat to use the appropriate compiler during installation.
Note: If the viewer file being used is an HTML file, then the TaskManager servlet opening the file makes a Web server request and returns pure HTML back to the TaskManager servlet for continued processing as XML. If, however, the viewer file is a .jsp file, then the TaskManager servlet opening the file makes a Web server request and the request goes into the JSP handler servlet, returning the executed JSP code and HTML to the TaskManager servlet for continued processing as XML.
If the viewer file being used is an HTML file, then the TaskManager servlet opening the file makes a Web server request and returns pure HTML back to the TaskManager servlet for continued processing as XML. If, however, the viewer file is a .jsp file, then the TaskManager servlet opening the file makes a Web server request and the request goes into the JSP handler servlet, returning the executed JSP code and HTML to the TaskManager servlet for continued processing as XML.
When writing Java Server Pages, you can write your own custom Java classes that you can call from your JSPs. To do this, you must edit the file:
<EPX>\bin\WebToolsServer.lax
There are a number of lax.class.path settings contained in this file. Enter the file path or paths for the .jar files you want to use.
For example:
lax.class.path=C:/Enterworks/EPX/jre/lib/rt.jar;