Problem when working with RichFaces (JSF) integrated into the spring with javax.faces.STATE_SAVING_METHOD=client. [SPR-5181]

[spring-projects-issues]

Emmanuel Ruiz Lopes opened SPR-5181 and commented

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

---

Issue Links:

• Provide ability to make aop:scoped-proxy prototypes and singletons truely serializable [SPR-2121] #6812 Provide ability to make aop:scoped-proxy prototypes and singletons truely serializable
• Service references in JSF session objects not restored when using persistent sessions [SPR-2675] #7364 Service references in JSF session objects not restored when using persistent sessions

[spring-projects-issues]

Juergen Hoeller commented

In general, serializability of Spring-managed objects is not a container concern. In other words, if serializability is important, you need to make sure that you design your components accordingly.

In the above case, it's unclear where that BeanFactory reference comes from: might be a BeanFactoryAware bean; might be a scoped proxy; might be something else. You'd have to debug this a bit further.

FYI, we do aim for serializability of Spring-generated proxies as fas as possible in Spring 3.0. So that part should be dealt with in 3.0. That's still a couple of months away, though.

Juergen

[spring-projects-issues]

Juergen Hoeller commented

This is finally making its way into Spring 3.0 now! See my comment on #6812...

Juergen