[
http://jira.jboss.com/jira/browse/RF-3306?page=all ]
Alexander Smirnov resolved RF-3306.
-----------------------------------
Fix Version/s: 3.2.1
(was: 3.2.2)
Resolution: Done
Ok, it was a workaround for a MyFaces 1.1.x / JSP environment bug.
I've removed StateManager instance checking code from Richfaces 3.2.1 code as
obsoletted.
custom StateManager not used
----------------------------
Key: RF-3306
URL:
http://jira.jboss.com/jira/browse/RF-3306
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4, 3.1.5
Environment: myFaces 1.1.5
tomahawk 1.1.5
tiles
jsps (no facelets)
Reporter: Michael Heinen
Assigned To: Alexander Smirnov
Fix For: 3.2.1
Custom StateManagers are not working in richFaces 3.1.5 and 3.1.4.
I defined a custom StateManager in faces-config:
<application>
<state-manager>com.MyStateManager</state-manager>
</application>
The stateManager is instantiated but not used for request processing.
This was working well with a4j 1.1.1
(I see this as a Blocker in richfaces)
--
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