JSP run time compilation settings

 

+

Search Tips   |   Advanced Search

 

By default, the JavaServer Pages engine translates a requested JSP file, compiles the .java file, and loads the compiled servlet into the run time environment. You can change the JSP engine default behavior by indicating that a JSP file must not be translated or compiled at run time, even when a .class file does not exist.

If run time compilation is disabled, precompile the JSP files, which provides the following advantages:

You can disable run time JSP file compilation on a global or an individual Web application basis:

If you disable run time compilation and a request arrives for a JSP file that does not have a matching .class file, the JSP engine returns HTTP error 500 (Internal server error) to the browser. In this case, an exception is written to the System Out (SYSOUT) and First Failure Data Capture (FFDC) logs.

If a JSP file has a matching .class file but that file is out of date, the JSP engine still loads the .class file into memory.


 

Related concepts

JavaServer Pages

 

Related tasks

Developing Web applications

 

Related Reference

Custom property settings
Web container custom properties