Provide options to compile JavaServer Pages settings
Specify options to be used by the JavaServer Pages (JSP) compiler.
This administrative console page is a step in the application installation and update wizards. To view this page, select Precompile JavaServer Pages files on the Select installations options page. Thus, to view this page, click...
Applications > New Application > New Enterprise Application > application_path > Next > Detailed - Show me all installation options and parameters > Next > Next or Continue > Precompile JavaServer Pages files > Next > Step: Provide options to compile JSPs.
We can specify the JSP compiler options on this page only when installing or updating an application containing web modules. After the application is installed, we must edit the JSP engine configuration parameters of a web module WEB-INF/ibm-web-ext.xmi file to change its JSP compiler options.
For IBM extension and binding files, the .xmi or .xml file name extension is different depending on whether we are using a pre-Java EE 5 application or module or a Java EE 5 or later application or module. An IBM extension or binding file is named ibm-*-ext.xmi or ibm-*-bnd.xmi where * is the type of extension or binding file such as app, application, ejb-jar, or web. The following conditions apply:
- For an application or module that uses a Java EE version prior to version 5, the file extension must be .xmi.
- For an application or module that uses Java EE 5 or later, the file extension must be .xml. If .xmi files are included with the application or module, the product ignores the .xmi files.
However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.
The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions.
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
Temporary class path for the JSP compiler to use when it is compiling JSP files 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 that are necessary for JSP compilation and are identified by other means, such as shared libraries, after the application is installed. In network deployment configurations, this class path is specific to the deployment manager machine.
To specify that multiple web modules use the same class path:
- In the list of web modules, select the Select check box for each web module to use a particular class path.
- Expand Apply Multiple Mappings.
- Specify the class path that we want.
- Click Apply.
Use full package names
Specifies 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 the web.xml file, 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 JSP files are not configured as servlets in the web.xml file.
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, 15,16, 17, and 18. The default is 17.
Disable JSP runtime compilation
Specifies 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 JSP files at run time; the JSP engine loads only precompiled class files. JSP source files do not need to be present to load class files. We can install an application without JSP source, but the application must have precompiled class files.
For a single web application 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:
Packages and directories for generated .java and .class files JSP engine Servlets JavaServer Pages JSP class loading settings Configure JSP engine parameters Install enterprise application files with the console JSP run time compilation settings web.xml file JavaServer Pages (JSP) runtime reloading settings