You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by dw...@apache.org on 2010/04/05 18:23:50 UTC
svn commit: r930896 -
/openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml
Author: dwoods
Date: Mon Apr 5 16:23:50 2010
New Revision: 930896
URL: http://svn.apache.org/viewvc?rev=930896&view=rev
Log:
OPENJPA-1597 Update docs to mention previous serialization side effects
Modified:
openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml
Modified: openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml
URL: http://svn.apache.org/viewvc/openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml?rev=930896&r1=930895&r2=930896&view=diff
==============================================================================
--- openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml (original)
+++ openjpa/branches/2.0.x/openjpa-project/src/doc/manual/migration_considerations.xml Mon Apr 5 16:23:50 2010
@@ -173,6 +173,16 @@
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
modified, so that by default all proxies will be removed
during serialization. See