JavaServer Faces migration
In WebSphere® Application Server V8.0 and later, the default JavaServer Faces (JSF) implementation has changed to MyFaces.
Choosing the correct JSF implementation
- Applications or dependant libraries that directly extend RI classes instead of JSF API classes.
- Applications that use context parameters that are specific to the RI and do not have an equivalent context parameter in MyFaces.
IBM JavaServer Faces widget library
You must update widget library to version 3.1.6 or higher to enable compatibility with the changes in the JSF 2.0 implementation. Obtain a compatible version of JWL by upgrading IBM® Rational® Application Developer for WebSphere to 7.5.5.2 or later or installing IBM Rational Application Developer for WebSphere V8.0 and later.
JSF 2.0 exception handling
The default behavior for JSF when unexpected exceptions occur during JSF lifecycle processing has changed. Prior to JSF 2.0, unexpected exceptions during lifecycle processing were hidden by the runtime environment. This behavior is no longer the case with JSF 2.0. Exceptions are now published to the new ExceptionHandler API, as described in section 6.2 of the JSF 2.0 specification.
<exception-handlerfactory>
javax.faces.webapp.PreJsf2ExceptionHandlerFactory
</exception-handlerfactory>