JSP and JSF option settings
Use this page to configure the class reloading of web modules such as JavaServer Pages (JSP) files and to select a JSF implementation to use with this application.
To view this administrative console page, click Provide JSP reloading options for web modules page on the application installation and update wizards.
. This page is the same as theHowever, 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
Specifies the name of a web module in the installed or deployed application.
URI
Specifies the location of the module that is relative to the root of the application (EAR file).
JSP enable class reloading
Specifies 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 Platform, Enterprise Edition 5 (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
Specifies the 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 you change the JSF implementation that you are using for your application, you must delete any previously compiled JSP files. If you precompiled your application, you must recompile. If you 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.
You 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 you change the JSF implementation that you are using for your application, you must delete any previously compiled JSP files. If you precompiled your application, you must recompile. If you did not precompile, but you already requested JSP files from this application, you must delete the JSP files from the temp directory of your profile.
You 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 Version 7 node uses MyFaces 1.2 if the MyFaces selection is toggled, while a Version 8 and later node uses MyFaces 2.0. For WebSphere® Application Server versions before Version 7 (for example, Version 6.1 and earlier), this toggle is ineffective because JSF implementation switching was not supported before Version 7.