JSP processor

When you configure your Web server instance to work with the WebSphere Application Server - Express for iSeries product, the Web server configuration is set to pass HTTP requests for JSP files (files with the extension .jsp) to WebSphere Application Server - Express. The JSP processor creates and compiles a servlet for each JSP file.

These following points apply to the JSP processor that is implemented in WebSphere Application Server - Express:

• The servlet that implements the JSP processor is org.apache.jasper.runtime.JspServlet.

• WebSphere Application Server - Express places the generated files in a temp directory under the WebSphere instance. For example, the WebSphere instance myInstance stores the generated files in

  /QIBM/UserData/WebASE/ASE5/myInstance/temp/node_name/
  application_server/enterprise_app/web_module

  where:

  • node_name is the name of the iSeries server or partition on which your WebSphere Application Server - Express instance is running
  • application_server is the name of your WebSphere Application Server - Express server
  • enterprise_app is the name of the enterprise application to which the JSP file belongs
  • web_module is the Web module that contains your JSP file.

  Note: This path has been wrapped for display purposes. Enter it as one path.

• When the processor generates the servlet, two or three files are created, depending on the JSP processor settings:

  • .class file
    This is the compiled servlet. This file is always created and kept.

  • .java file
    This is the generated source (.java) file. This file is created during the compilation of a JSP page, but the processor only keeps the file if it is told to do so. You can retain the .java file by setting an initialization parameter (for the JSP attributes) called keepgenerated to a value of true. This setting leaves the generated .java file in the /QIBM/UserData/WebASE/ASE5/instance/temp/node_name/ application_server/enterprise_app/web_module directory. By default this value is not specified as an init parameter, and thus the default behavior is to not keep the generated .java file.

  • .dat file
    This contains the static (HTML code and text content) part of the original JSP file.

• workingDir is an init() parameter that is specified by default. However, this parameter is ignored by the JSP processor.

Keeping generated Java source files

The JSP processor generates a Java source file for each JSP file. By default, this file is deleted immediately. It is recommended that you keep the generated .java file for debugging purposes only. It is safer and more efficient to configure the JSP processor to delete generated .java files in a production environment.