[
https://issues.apache.org/jira/browse/OPENJPA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1597:
----------------------------------
Attachment: OPENJPA-1597-trunk-20100327.patch
OPENJPA-1597-trunk-compat.patch
Patches that add a new openjpa.Compatibility flag of
IgnoreDetachedStateFieldForProxySerialization, which when 2.0 apps set to TRUE,
will use the old 1.0 behavior for Proxies.writeReplace(), along with
automatically using the old behavior for 1.0 apps.
Patch file 20100327 reverts a previous addition of removing proxies when they
are detached, which broke a detach/merge scenario when using proxied List
collections.
> Need Compatibility setting for new OPENJPA-1097 Proxies and
> DetachedStateField behavior
> ---------------------------------------------------------------------------------------
>
> Key: OPENJPA-1597
> URL: https://issues.apache.org/jira/browse/OPENJPA-1597
> Project: OpenJPA
> Issue Type: Bug
> Components: integration, jpa, UnenhancedClasses
> Affects Versions: 2.0.0-beta3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1597-12x-tests.patch,
> OPENJPA-1597-20x-tests-fix.patch, OPENJPA-1597-20x-tests.patch,
> OPENJPA-1597-trunk-20100327.patch, OPENJPA-1597-trunk-compat.patch,
> OPENJPA-1597-trunk-tests-fix.patch, OPENJPA-1597-trunk-tests.patch
>
>
> Need Compatibility setting for new Proxies and DetachedStateField behavior
> introduced in OPENJPA-1097 for legacy 1.0 persistence.xml apps, that rely on
> old behavior that using DetachedStateField=true would remove $proxy usage
> when serialized, but the new behavior is to keep the $proxy usage since we
> are serializing the StateManager into the object....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
