openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] Updated: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
Date Mon, 07 Feb 2011 23:22:57 GMT


Mark Struberg updated OPENJPA-1933:

    Attachment: OPENJPA-1933-test-2.patch

This test shows the problems. After the deserialization, the elementCollectionLazy contains
just a java.util.List and not a proxy anymore. Thus, the subsequent adding a value to the
ElementCollection will not result in a database update.

Question: should the proxy should get serialized, or should it only get 'restored' if deserialized

> @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