[richfaces-issues] [JBoss JIRA] Resolved: (RF-4547) Problem when working with RichFaces (JSF) integrated into the spring with javax.faces.STATE_SAVING_METHOD=client.
Nick Belaevski (JIRA)
jira-events at lists.jboss.org
Sun Sep 28 14:21:31 EDT 2008
[ https://jira.jboss.org/jira/browse/RF-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Belaevski resolved RF-4547.
--------------------------------
Resolution: Incomplete Description
Assignee: Tsikhon Kuprevich
> Problem when working with RichFaces (JSF) integrated into the spring with javax.faces.STATE_SAVING_METHOD=client.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-4547
> URL: https://jira.jboss.org/jira/browse/RF-4547
> Project: RichFaces
> Issue Type: Bug
> Affects Versions: 3.2.2
> Environment: windows XP
> Reporter: Emmanuel Ruiz Lopes
> Assignee: Tsikhon Kuprevich
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The problem happens when I use a bean in the requisition scope (JSF), however I use a tag of the framework <rich:keepAlive beanName = ' <Bean> '> <http://livedemo.exadel.com/richfaces-demo/richfaces/keepAlive.jsf?c=keepAlive&tab=usage> that maintains it alive among the requisitions. You works perfectly when the configuration javax.faces.STATE_SAVING_METHOD=server, the problem happens when I use javax.faces.STATE_SAVING_METHOD=client (web.xml). In this last configuration, the tree of components of JSF is seriarizable and saved in the client. At this time it happens the following mistake:
>
> java.io.NotSerializableException: org.springframework.beans.factory.support.DefaultListableBeanFactory
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list