WAS v8.5 > Reference > SetsJSP and JSF option settings page
Use this page to configure the class reloading of web modules such as JSP files and to select a JSF implementation to use with this application.
To view this dmgr console page, click Applications > Application Types > WebSphere enterprise applications > application_name > JSP and JSF options. This page is the same as the Provide JSP reloading options for web modules page on the application installation and update wizards.
The following note applies to the files with an .xmi extension in this topic:
For IBM extension and binding files, the .xmi or .xml file name extension is different depending on whether you 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 apps and modules that use a Java EE version prior to version 5, the file extension must be .xmi.
- For apps and modules that use 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. sptcfg
Web module
Name of a web module in the installed or deployed application.
URI
Location of the module that is relative to the root of the application (EAR file).
JSP enable class reloading
Whether to enable class reloading when JSP files are updated.
A web container reloads JSP files only when the IBM extension reloadEnabled in the jspAttributes of the ibm-web-ext.xmi file is set to true.
Java EE 5 and later applications IBM extension files are in .xml file format. For applications versions earlier than Java EE 5, they are in the .xmi file format.
JSP reload interval in seconds
Number of seconds to scan the application file system for updated JSP files. The default is the value of the reloading interval attribute in the IBM extension (META-INF/ibm-web-ext.xmi) file of the web module.
To enable reloading, specify a value greater than zero (for example, 1 to 2147483647). The default reload interval is 5. To disable reloading, specify zero (0). The range is from 0 to 2147483647.
The reloading interval attribute takes effect only if class reloading is enabled.
Java EE 5 applications and later IBM extension files are in .xml file format. For applications versions earlier than Java EE 5, they are in the .xmi file format.
Sun Reference Implementation 1.2
Select this option to use the Sun Reference Implementation 1.2 JSF implementation.
If we change the JSF implementation that you are using for the application, you must delete any previously compiled JSP files. If we precompiled the application, you must recompile. If we did not precompile, but have already requested JSP files from this application, you must delete the JSP files from the temp directory of your profile.
We can set the JSF engine configuration parameter, com.ibm.ws.jsf.JSF_IMPL_CHECK, to true to automatically mark the JSP files to recompile at application startup.
MyFaces 2.0
Select this option to use the MyFaces JSF implementation. This is the default JSF implementation.
If we change the JSF implementation that you are using for the application, you must delete any previously compiled JSP files. If we precompiled the application, you must recompile. If we did not precompile, but have already requested JSP files from this application, you must delete the JSP files from the temp directory of your profile.
We can set the JSF engine configuration parameter, com.ibm.ws.jsf.JSF_IMPL_CHECK, to true to automatically mark the JSP files to recompile at application startup.
In a mixed-version cell, a v7 node uses MyFaces 1.2 if the MyFaces selection is toggled, while a v8 and later node uses MyFaces 2.0. For WebSphere Application Server versions before v7 (for example, v6.1 and earlier), this toggle is ineffective because JSF implementation switching was not supported before v7.
Related concepts:
Servlets
JSP
JSP class loading settings
Related
Install enterprise application files with the console
Configure enterprise application files
Configure JSF engine parameters
Configure JavaServer Faces implementation
Reference:
Enterprise application settings
web.xml file
JSP runtime reloading settings