JSF engine configuration parameters

In WebSphere® Application Server, you can configure the JavaServer Faces (JSF) engine configuration parameters for optimal performance in a production server environment and for the needs of developers in a development environment.

The JSF engine parameters are case sensitive. If the value specified for a parameter is comprised of two or more words separated by spaces, you must add quotation marks around the value.

JSF options using SUN RI

  • com.sun.faces.numberOfViewsInSession

    Specifies the number of views that are stored in the session when Server-Side State Saving is used. If set to true while client-side state saving is being used, reduces the number of bytes sent to the client by compressing the state before it is encoded and written as a hidden field. The default for this parameter is 15.

  • com.sun.faces.numberOfLogicalViews

    Specifies the number of logical views that are stored in the session when Server-Side State Saving is used. The default for this parameter is 15.

  • com.sun.faces.injectionProvider

    Defines an injection provider that is used for JSF annotations.

  • com.sun.faces.serializationProvider

    Defines a serialization provider that is used for serializing JSF objects into session.

  • com.sun.faces.responseBufferSize

    Define the size of the response buffer for a JSF response. The default for this parameter is 1048.

  • com.sun.faces.clientStateWriteBufferSize

    The default for this parameter is 8192.

  • com.sun.faces.clientStateTimeout

    The timeout value used for client side state saving. Once the value set has been reached then the state is lost. Default is infinite.

  • com.sun.faces.displayConfiguration

    The default for this parameter is false.

  • com.sun.faces.validateXml

    The default for this parameter is false.

  • com.sun.faces.verifyObjects

    The default for this parameter is false.

  • com.sun.faces.disableVersionTracking

    The default for this parameter is false.

  • com.sun.faces.prererXHTML

    The default for this parameter is false.

  • com.sun.faces.compressViewState

    The default for this parameter is true.

  • com.sun.faces.compressJavaScript

    The default for this parameter is true.

  • com.sun.faces.externalizeJavaScript

    The default for this parameter is false.

  • com.sun.faces.sendPoweredByHeader

    The default for this parameter is true.

  • com.sun.faces.enableJSStyleHiding

    The default for this parameter is false.

  • com.sun.faces.writeStateAtFormEnd

    The default for this parameter is true.

  • com.sun.faces.enableLazyBeanValidation

    The default for this parameter is true.

  • com.sun.faces.enableLoadBundle11Compatibility

    The default for this parameter is false.

  • com.sun.face.serializeServerState

    The default for this parameter is false.

JSF options for MyFaces

JSF options using SUN RI or MyFaces

The following options are valid for both the SUN RI and the MyFaces implementations.
  • javax.faces.STATE_SAVING_METHOD

    Specifies the location where state information is saved. Valid values are 'server', which is saved in HttpSession, and 'client', which is saved as a hidden field in the form. The default for this parameter is server.

  • javax.faces.CONFIG_FILES

    Use this parameter to specify a comma-delimited list of context-relative resource paths under which the JSF implementation looks for application configuration resources before loading a configuration resource named /WEB-INF/facesconfig.xml, if a resource exists.

  • javax.faces.DEFAULT_SUFFIX

    Specifies the default suffix for extension-mapped resources that contain JSF components. The default for this parameter is .jsp.

  • javax.faces.LIFECYCLE_ID

    Use this parameter to configure an alternate lifecycle ID.

  • com.ibm.ws.jsf.JSF_IMPL_CHECK

    Specifies that the JSP files in a Web module must be recompiled when the application is restarted because the implementation of JSF that is used has changed. After the application is restarted, the next time a JSP files is accessed for this module the JSP is recompiled against the selected implementation of JSF specified in the administration console. Subsequent calls to the JSP do not cause a recompile. The default setting for this option is false. Use this option for development and not in a production environment.

IBM options for JSF runtime

  • com.ibm.ws.jsf.JSP_UPDATE_CHECK

    This parameter monitors Faces JavaServer Pages (JSP) files for modifications and synchronizes a running server with the changes without restarting the server. If this parameter is set to false or removed from the deployment descriptor, any changes made to Faces JSP files might not be seen by the server until it is restarted. Set this parameter to true while developing and debugging the Faces JSP files to improve the performance of the development environment.

  • com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP

    Specifies to load the JSF runtime when the application server starts up. If this parameter is set to false or removed, JSF runtime is loaded and initialized when the first JSF request is processed. This might disable custom JSF extensions such as factories defined in the project.

  • com.ibm.ws.jsf.JSF_IMPL_CHECK

    Set the com.ibm.ws.jsf.JSF_IMPL_CHECK parameter to true to check at application restart if the SUN RI and MyFaces implementations were switched. If the implementation has switched, then the runtime removes any generated JSP files from the temp directory and the JSP file is retranslated the next time it is requested.




Related concepts
JavaServer Faces
Related tasks
Configuring JSF engine parameters
Configuring JavaServer Faces implementation
Managing JavaServer Faces implementations using wsadmin scripting
Related reference
JSF engine configuration parameters
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rweb_jsfengine
File name: rweb_jsfengine.html