openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
Date Tue, 08 Feb 2011 19:51:57 GMT


Mark Struberg commented on OPENJPA-1933:

puh, pretty hard to reproduce in our test suite. Guess this goes hand in hand with having
the enhancer.xml almost unmaintainable in the meantime. The 

As a result, I've created an own openjpa-reg-tests (regression tests) module which contains
1 subproject for each JIRA issue and gets activated with the profile 'reg-tests'.

Each JIRA issue is clearly reproducable this way and doesn't interfere with other configuration

> @ElementCollection loose proxytype after serialisation
> ------------------------------------------------------
>                 Key: OPENJPA-1933
>                 URL:
>             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-2.patch, OPENJPA-1933-test.patch
> usually an @ElementCollection field loaded from the database will be created as a$.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:


View raw message