Apache/openjpa
1
0
Fork 0
mirror of https://github.com/apache/openjpa.git synced 2025-03-09 01:59:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

OPENJPA-1597 Update docs to mention previous serialization side effects

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@930888 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Donald Woods 2010-04-05 15:56:21 +00:00
parent 670d59ef0f
commit b2d71bbe4d
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
openjpa-project/src/doc/manual/migration_considerations.xml
View File

@ -168,9 +168,19 @@
In 1.x.x releases of OpenJPA, when an entity was serialized
after calling EntityManager.find(), detach() or detachAll()
then all <xref linkend="ref_guide_pc_scos_proxy"/>
were removed as expected, but when the same entity instance
was serialized after calling EntityManager.clear() the
proxy classes were not removed.
references were removed as expected, but when the same
entity instance was serialized after calling
EntityManager.clear() the proxy classes were not removed.
</para>
<para>
This has two side-effects:
when entities are remoted across JVM boundaries (RPC)
or deserialized the OpenJPA runtime must be available
on the classpath (both client and server containers);
when entities are deserialized the OpenJPA runtime must
be the exact same revision as used to serialize the
entities due to the $proxy classes using dynamically
generated serialVersionUID values.
</para>
<para>
Starting with OpenJPA 2.0, this behavior has been