Mojarra 2.0.5 Release Notes
Release Notes

This document contains information that should help you use this software library more effectively. See the JSF FAQ for additional information.

Java ^TM 2 Platform, Standard Edition (J2SE ^TM ) Requirements

This release of JSF requires J2SE 5.0 or higher.

Webtier Specification Requirements

This release of JSF requires:

• Java Servlet 2.5
• JavaServer ^TM Pages 2.1
• JavaServer ^TM Pages Standard Tag Library 1.2

General Comments on the Mojarra 2.0.5 Release

This release should be considered feature complete with the JavaServer Faces 2.0 specification.

Identifying the JAR Files

Installing Mojarra 2.0.5 on GlassFish v2

• download the Mojarra 2.0.5 binary bundle from the project page
• backup your existing jsf-impl.jar found in GF_HOME/lib
• copy the new jsf-api and jsf-impl JARs to GF_HOME/lib
• edit your GF_HOME/domains/<domain-name>/config/domain.xml and add (or update the existing classpath-prefix) 'classpath-prefix="${com.sun.aas.installRoot}/lib/jsf-api.jar" to the java-config element
• restart your server

Installing Mojarra 2.0.5 on GlassFish v3 (including GlassFish Prelude)

• download the Mojarra 2.0.5 binary bundle from the project page
• backup your existing jsf-impl.jar found in GF_HOME/modules
• copy the new jsf-api and jsf-impl JARs to GF_HOME/modules
• restart your server

Uninstalling Mojarra 2.0.5 on GlassFish v3 (including GlassFish Prelude)

It is critical when uninstalling Mojarra 2.0.5, that you also reinstall the 1.2 version of JSF. The admin console of glassfish requires JSF to function correctly.

Configuring your web application to use Mojarra 2.0.5

NOTE: JSP-based JSF 1.2 applications should deploy and run without issue using Mojarra 2.0.5, however, the bulk of the new features defined will only work with Facelets (specifically the Facelets implementation included in jsf-impl.jar). If you decided to test your existing Facelets-based JSF 1.2 application, make sure you do not include the jsf-facelets.jar with your application.

With JSF 2.0, there is now a set of rules that are followed to determine whe the Facelets included with Mojarra 2.0.5 will be disabled. See the following list:

• if /WEB-INF/faces-config.xml is versioned at 1.2 or older, JSF 2.0 Facelets will not be used. Make sure the version and web-facesconfig.xml schema reference are versioned at 2.0
• If any of the faces-config.xml files reference the com.sun.facelets.FaceletViewHandler, JSF 2.0 Facelets will not be used. This allows for easy migration compatibility for those applications that have direct dependencies on Facelet classes.

With the release of JSF 2.0, it is possible to use both JSP and Facelets in the same application using *both* prefix and extension mapping for the FacesServlet. See the updated documentation for ViewHandler.DEFAULT_SUFFIX_PARAM for details on how the new algorithm works.

Change Log

• Mojarra 2.0.5 - What's New
• Mojarra 2.0.5 - Resolved Issues

Known Issues

• Mojarra 2.0.5 - Known Issues