[jira] [Updated] (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
[ 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)
[jira] [Updated] (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
[ 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
[jira] Updated: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
[ https://issues.apache.org/jira/browse/OPENJPA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-1933: --- Attachment: openjpa-reg-tests.tar.gz this needs the openjpa-tools being activated first see OPENJPA-1934 @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 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 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
[ https://issues.apache.org/jira/browse/OPENJPA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 again? @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 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 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENJPA-1933) @ElementCollection loose proxytype after serialisation
[ https://issues.apache.org/jira/browse/OPENJPA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-1933: --- Attachment: OPENJPA-1933-test.patch this patch extends a previous test which shows the problem. It currently fails to detach the lazy loaded ElementCollection @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 Reporter: Mark Struberg Priority: Critical Fix For: 2.2.0 Attachments: OPENJPA-1933-test.patch 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
