JavaServer(TM) Faces 1.2
Known issues with the 1.2_14 release.
The default renderer for
h:dataTable doesn't produce accessible markup - specifically no
scope attribute is rendered on table rows (see issue
When upgrading from 1.2 to a later 1.2_0x release 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 or later 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.
Groovy support fails in recent builds of GlassFish V3 (which includes 1.2_14) when installing groovy-1.5.5-all.jar (or later) as an OSGi bundle in the v3 modules directory (currently, this is the only way to make Groovy available to JSF).
When attempting to resolve a Groovy resource, the following error may occur:
BUG! exception in phase 'semantic analysis' in source unit ...
The problem is due to groovy-1.5.5-all.jar not exporting all of the packages necessary to resolve the classes needed to compile a groovy source file at runtime.
We've logged GROOVY-3001 to UPDATE: Use the latest Groovy 1.6 BETA to resolve the issue.