openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
Date Wed, 23 Feb 2011 03:35:38 GMT


Michael Dick commented on OPENJPA-1933:

To answer your question, IgnoreDetachedStateFieldForProxySerialization is only when we replace
a proxy field ( so collections, or temporal fields). It doesn't bleed into other parts of
the code. 

But you shouldn't have to use it - if you have a DetachedStateManager (that should be some

> @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, openjpa-reg-tests.tar.gz
> 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