[jira] [Updated] (OPENJPA-1933) @ElementCollection loose proxytype after serialisation

["Albert Lee (Updated) (JIRA)" <ji...@apache.org>]

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

Albert Lee updated OPENJPA-1933:
--------------------------------

    Affects Version/s: 2.2.0
                       2.1.1
        Fix Version/s:     (was: 2.2.0)
                       2.3.0

Move fix version to 2.3.0 in preparation for 2.2.0 release.
                
> @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.3.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira