[
http://jira.jboss.com/jira/browse/RF-2294?page=all ]
Alexander Smirnov resolved RF-2294.
-----------------------------------
Fix Version/s: 3.1.5
Resolution: Won't Fix
This is not a bug, just SUN RI feature.
Sun JSF 1.2 implementation detect ViewHandler / StateManager version from faces-config.xml
DTD/XML schema name. We can't switch RichFaces 3.1.x configuration files to a JSF 1.2
format, as far as it will completely break JSF 1.1 compatibility.
Fortunately, there is workaround for a SUN RI framework. Just put :
<context-param>
<param-name>com.sun.faces.disableVersionTracking</param-name>
<param-value>true</param-value>
</context-param>
into application web.xml. It will switch framework to a JSF 1.2 behavior.
Exception handling - Fix the JSF RI ViewExpiredException
--------------------------------------------------------
Key: RF-2294
URL:
http://jira.jboss.com/jira/browse/RF-2294
Project: RichFaces
Issue Type: Bug
Reporter: Shane Bryzak
Assigned To: Alexander Smirnov
Priority: Critical
Fix For: 3.1.5
If you submit an h:form on a timed out session, you expect that
exception - you need it to handle session timeout gracefully. I can
not get the JSF RI to throw that exception even with a Hello World
test, the form is processed on the new session without complaint -
running into further problems because your state is not there.
Probably involves writing a simple test case and submitting it to Sun.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira