[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3623) Make at least ListProxy serializable
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3623?page=c...
]
Adam Warski commented on HHH-3623:
----------------------------------
But if a snapshot is saved, before the list is accessed (and read), and then restored (as
I understand, possibly in a different request, so with a different Session/EntityManager),
then reading the list will cause an error.
Though I'll make the classes serializable in case you read the list before
snapshotting :).
Make at least ListProxy serializable
------------------------------------
Key: HHH-3623
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3623
Project: Hibernate Core
Issue Type: Bug
Components: envers
Environment: Hibernate 3.3.1, MySQL Server 5.0
Reporter: Mircea Gaceanu
In Spring WebFlow all objects used in a flow need to be serializable (because it has a
"snapshotting" mechanism that saves flow states, so all the objects used in the
flow).
See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145575 for other
details.
For me making ListProxy implement Serializable and adding no-arg constructors to
ListProxy and CollectionProxy fixed the problem, although I believe the other proxy
classes should be serializable too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira