openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
Date Tue, 29 Oct 2013 08:12:31 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Struberg updated OPENJPA-1933:
-----------------------------------

    Fix Version/s:     (was: 2.3.0)
                   2.4.0

> @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, 2.1.1, 2.2.0
>            Reporter: Mark Struberg
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: OPENJPA-1933-test-2.patch, OPENJPA-1933-test.patch, openjpa-reg-tests.tar.gz
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message