openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dwo...@apache.org
Subject svn commit: r930888 - /openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml
Date Mon, 05 Apr 2010 15:56:21 GMT
Author: dwoods
Date: Mon Apr  5 15:56:21 2010
New Revision: 930888

URL: http://svn.apache.org/viewvc?rev=930888&view=rev
Log:
OPENJPA-1597 Update docs to mention previous serialization side effects

Modified:
    openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml

Modified: openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml?rev=930888&r1=930887&r2=930888&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml Mon Apr  5 15:56:21
2010
@@ -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



Mime
View raw message