JavaServer(TM) Faces 1.2
|
JSF Community
|
Known issues with the 1.2_08 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).
When upgrading from 1.2 to 1.2_01, 1.2_02, or 1.2_03, 1.2_04, or 1.2_05 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.
In 1.2_08, if the total length (in characters) of all attribute name/value pairs for a particular element is greater than 1024, an IndexOutOfBoundsException is thrown. This issue was introduced as a side effect of attempting to optimize the number of direct writes made by the HtmlResponseWriter. This is currently fixed in the nightlies. See issue 705 for details.