JSP and JSF option settings

To configure the class reloading of Web modules such as JSPs and to select a JSF implementation to use with this application.

To view this admin console panel, click Applications > Application Types > WebSphere enterprise apps > application_name > JSP and JSF options. This panel is the same as the Provide JSP reloading options for Web modules panel on the application installation and update wizards.

Web module

Name of a Web module in the installed or deployed application.

URI

Location of the module relative to the root of the application (EAR file).

JSP enable class reloading

Whether to enable class reloading when JSPs are updated.

A Web container reloads JSPs only when the IBM extension reloadEnabled in the jspAttributes of the ibm-web-ext.xmi file is set to true.

J2EE 5 applications IBM extension files are in .xml file format. For applications versions earlier than J2EE 5, they are in the .xmi file format.

JSP reload interval in seconds

Number of seconds to scan the application's file system for updated JSPs. 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.

J2EE 5 applications IBM extension files are in .xml file format. For applications versions earlier than J2EE 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. This is the default JSF implementation.

If we change the JSF implementation that we are using for the application, delete any previously compiled JSPs. If we precompiled the application, recompile. If we did not precompile, but have already requested JSPs from this application, delete the JSPs from the temp directory of the profile.

We can set the JSF engine configuration paramater, com.ibm.ws.jsf.JSF_IMPL_CHECK, to true to automatically mark the JSPs to recompile at application startup.

MyFaces 1.2

Select this option to use the MyFaces 1.2 JSF implementation.

If we change the JSF implementation that we are using for the application, delete any previously compiled JSPs. If we precompiled the application, recompile. If we did not precompile, but have already requested JSPs from this application, delete the JSPs from the temp directory of the profile.

We can set the JSF engine configuration paramater, com.ibm.ws.jsf.JSF_IMPL_CHECK, to true to automatically mark the JSPs to recompile at application startup.

---

Related concepts

Servlets
JSPs
JSP class loading settings

 

Related tasks

Install enterprise application files with the console
Set enterprise application files
Set JSF engine parameters
Set Java Server Faces implementation

 

Related

Enterprise application settings
web.xml file
JSPs runtime reloading settings