JavaServer ^TM Faces Release Notes
Known Issues

Known issues with the 1.2_05 FCS release.

• The default renderer for h:dataTable doesn't produce accessible markup - specifically no scope attribute is rendered on table rows (see issue 341).

• If rendering multiple forms in the same view, and attempting to validate via the W3C validator, there will be warnings regarding duplicate IDs (javax.faces.ViewState). The spec currently requires that for each Form we output the state info with the ID and Name of javax.faces.ViewState.

• When upgrading from 1.2 to 1.2_01, 1.2_02, or 1.2_03, 1.2_04, on Tomcat 5.x with Facelets, the user may receive a ClassNotFoundException for com.sun.faces.config.GlassFishConfigureListenener. In order to resolve this, delete the tld cache references under TOMCAT_HOME/work and restart the server.

• When upgrading to 1.2_05 while running on a Servlet 2.4 container the following error may be encountered:

                com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED!Unable to parse document 'file:/C:/develop/Java/Tomcat
  -5.5.25/work/Catalina/localhost/server/loader/com/sun/faces/jsf-ri-runtime.xml': This parser does not support specificat
  ion "null" version "null"
            

  This error indicates the version of JAXP being used with the container is not compliant with JAXP 1.3 or later. Refer to the container's documentation for details on how to upgrade JAXP.

• In the JSF-RI 1.1 series it was possible to use jsp:include with nested jsp:params. This is no longer possible with JSF-RI 1.2. This is not a true backwards compatibility issue. The fact that it worked in 1.1 was due to a side-effect of a workaround for a Tomcat 4 bug. Had this workaround be removed, usage of jsp:param would have failed. We've evaluated potential ways to enable this functionality in 1.2, but have decided that this issue will not be resolved.

• ADDED 10/22/2007

  There is an apparent problem with the 1.2_05 GlassFish updater where the classpath-prefix of the domain isn't properly updated and no error condition is reported. Due to this issue, we recommend that you do not use the updater if you already have downloaded it locally.

  The following steps detail the manual upgrade process:

  • download the 1.2_05 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 'classpath-prefix="${com.sun.aas.installRoot}/lib/jsf-api.jar" to the java-config element
  • restart your server

• ADDED 11/12/2007

  A regression was introduced in the renderer for h:outputLink where the target attribute is no longer rendered. This will be addressed in the next release (the fix is already available in the nightly builds).