Provide options to compile JSPs settings
To specify options to be used by the JSPs compiler.
This admin console panel is a step in the application installation and update wizards. To view this panel, select Precompile Java Server Pages files on the Select Installation options panel. Thus, to view this panel, click Applications > New application application_path > Show me all installation options and parameters > Next > Next > Precompile JSPs > Next > Step: Provide options to compile JSPs.
We can specify the JSP compiler options on this panel only when installing or updating an application that contains Web modules. After the application is installed, edit the JSP engine configuration parameters of a Web module's WEB-INF/ibm-web-ext.xmi file to change its JSP compiler options.
- Web module
Name of a module within the application.
- URI
Location of the module relative to the root of the application (EAR file).
- JSP class path
Specifies a temporary class path for the JSP compiler to use when compiling JSPs during application installation. This class path is not saved when the application installation is complete and is not used when the application is running. This class path is used only to identify resources outside of the application which are necessary for JSP compilation and which will be identified by other means (such as shared libraries) after the application is installed. In network deployment configurations, this class path is specific to the dmgr machine.
To specify that multiple Web modules use the same class path:
- In the list of Web modules, select the Select check box beside each Web module to use a particular class path.
- Expand Apply Multiple Mappings.
- Specify the desired class path.
- Click Apply.
- Use full package names
Whether the JSP engine generates and loads JSP classes using full package names.
When full package names are used, precompiled JSP class files can be configured as servlets in web.xml, without having to use the jsp-file attribute. When full package names are not used, all JSP classes are generated in the same package, which has the benefit of smaller file-system paths.
When the options useFullPackageNames and disableJspRuntimeCompilation are both true, a single class loader is used to load all JSP classes, even if the JSPs are not configured as servlets in web.xml.
This option is the same as the useFullPackageNames JSP engine parameter.
- JDK source level
Source level at which the Java ™ compiler compiles JSP Java sources. Valid values are 13, 14, and 15. The default value is 13, which specifies source level 1.3.
- Disable JSP runtime compilation
Whether a JSP file should never be translated or compiled at run time, even when a .class file does not exist.
When this option is set to true, the JSP engine does not translate and compile JSPs at run time; the JSP engine loads only precompiled class files. JSP source files do not need to be present in order to load class files. We can install an application without JSP source, but the application must have precompiled class files.
For a single Web app class loader to load all JSP classes, this compiler option and the Use full package names option both must be set to true.
This option is the same as the disableJspRuntimeCompilation JSP engine parameter.
Related concepts
Packages and directories for generated .java and .class files
JSP engine
Servlets
JSPs
JSP class loading settings
Related tasks
Set JSP engine parameters
Install enterprise application files with the console
Related
JSP run time compilation settings
web.xml file
JSPs runtime reloading settings