You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2011/02/01 17:22:28 UTC
[jira] Updated: (OPENJPA-1933) @ElementCollection loose proxytype
after serialisation
[ https://issues.apache.org/jira/browse/OPENJPA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg updated OPENJPA-1933:
-----------------------------------
Attachment: OPENJPA-1933-test.patch
this patch extends a previous test which shows the problem. It currently fails to detach the lazy loaded ElementCollection
> @ElementCollection loose proxytype after serialisation
> ------------------------------------------------------
>
> Key: OPENJPA-1933
> URL: https://issues.apache.org/jira/browse/OPENJPA-1933
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Mark Struberg
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: OPENJPA-1933-test.patch
>
>
> usually an @ElementCollection field loaded from the database will be created as a org.apache.openjpa.java$.util$.ArrayListProxy.
> After serialisation/deserialisation (with DetachedStateField=true) the List will be recreated as standard java.util.ArrayList.
> This has the bad side effect, that any subsequent add to this ElementCollection will not set the _dirty field in the DetachedStateManager and any changes in the ElementCollection will not get saved to the database.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira