OPENJPA-1597 Migration doc updates to mention the new Compatibility flag.

git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@928854 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Donald Woods 2010-03-29 18:10:16 +00:00
parent 371a31a41a
commit 137071d9bf
1 changed files with 12 additions and 2 deletions

View File

@ -163,7 +163,7 @@
<title> <title>
Serialization of Entities Serialization of Entities
</title> </title>
<!-- See OPENJPA-1097 for details. --> <!-- See OPENJPA-1097 and OPENJPA-1597 for details. -->
<para> <para>
In 1.x.x releases of OpenJPA, when an entity was serialized In 1.x.x releases of OpenJPA, when an entity was serialized
after calling EntityManager.find(), detach() or detachAll() after calling EntityManager.find(), detach() or detachAll()
@ -173,7 +173,7 @@
proxy classes were not removed. proxy classes were not removed.
</para> </para>
<para> <para>
Starting with OpenJPA 1.3 and 2.0, this behavior has been Starting with OpenJPA 2.0, this behavior has been
modified, so that by default all proxies will be removed modified, so that by default all proxies will be removed
during serialization. See during serialization. See
<xref linkend="ref_guide_pc_scos_proxy_serial"/> <xref linkend="ref_guide_pc_scos_proxy_serial"/>
@ -183,6 +183,16 @@
for more details on how to override the default for more details on how to override the default
<literal>DetachedStateField</literal> setting. <literal>DetachedStateField</literal> setting.
</para> </para>
<para>
Applications that use a 1.0 persistence.xml will
automatically maintain the old behavior. It is
possible for a version 2.0 application to revert back to
the prior 1.x.x behavior by setting the following
openjpa.Compatibility property as follows:
<simplelist>
<member>IgnoreDetachedStateFieldForProxySerialization=true</member>
</simplelist>
</para>
</section> </section>
</section> </section>
<section id="Disabling AutoOff Collection Tracking"> <section id="Disabling AutoOff Collection Tracking">