Java Server Faces (JSF) Applications

In WebSphere Application Server V8.0, the default Java Server Faces (JSF) engine changed to MyFaces 2.0. In previous releases of WebSphere, the default engine was the Sun Reference Implementation for JSF. In WebSphere Application Server V9.0, the JSF SunRI engine is removed.

When migrating JSF applications to WebSphere V8.0, V8.5.5, or Liberty, you can choose to migrate your application to use the included MyFaces implementation, configure WebSphere V8.0 or V8.5.5 to use the older Sun Reference Implementation as the default JSF engine, or package your preferred JSF engine with your application.

When migrating to WebSphere V9.0, you can migrate your application to use the included MyFaces implementation or package your preferred JSF engine with your application.

This rule is flagged only once per Eclipse project or Java archive where JSF artifacts are found. The rule will generate a result if any of the following conditions are true:

• If a web.xml file contains a listener-class element where the value starts with com.sun.faces.
• If the file is an XML file, and its root element is faces-config and has no DTD information and the version is set to 1.2.
• If the file is an XML file, and its root element is faces-config and has DTD information with a system ID set to:
  • http://java.sun.com/dtd/web-facesconfig_1_0.dtd or
  • http://java.sun.com/dtd/web-facesconfig_1_1.dtd
• If Java code has references to the com.sun.faces package

For additional information see:

• JavaServer Faces
• Configuring JavaServer Faces implementation
• Managing JavaServer Faces implementations using wsadmin scripting
• Configuring JSF engine parameters
• Removed features of WebSphere Application Server traditional Version 9.0