JSP run time compilation settings

By default, the JavaServer Pages (JSP) 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, you must 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 the following 404 error to the browser:
Error 404: SRVE0200E: Servlet [org.apache.jsp._jsp1]: Could not find required servlet class - _jsp1.class
[AIX Solaris HP-UX Linux Windows][IBM i]In this case, an exception is written to the System Out (SYSOUT) and First Failure Data Capture (FFDC) logs. [z/OS]In this case, an exception is written to the joblog (SYSPRINT) file if the ras_trace_outputLocation property in the was.env file is set to SYSPRINT, or to CTRACE if ras_trace_outputLocation is set to BUFFER.

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.


指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:14
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rweb_jspdis
檔名:rweb_jspdis.html