You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org> on 2012/01/17 21:15:39 UTC
[jira] [Updated] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Leimer updated OPENJPA-2110:
-------------------------------------
Description:
When using an abstract entity, all collections defined in this super class are incorrectly filled in with standard OpenJPA collection implementations. But I want to have my own collection implementation inside my entities.
E.g.: private Set<Item> items = new MyHashSet<Item>();
should be a specialized collection proxy, but when an abstract entity comes in only the standard OpenJPA collection proxy is used.
I proved this statement by creating two Eclipse sample projects which you can find in the attachments of this ticket. This problem occures in both of the newest version of OpenJPA.
To execute the JUnit test go to src/openjpa/test/FailingTest.java and hit run. You will see an error displayed in the console. To get this test case green only openjpa.model.AbstractCategory has to be "unabstract". Just remove "abstract" in its class definition.
I hope my informations help you to fix this issue in a reasonable time.
was:
When using an abstract entity, all collections defined in this super class are incorrectly filled in with standard OpenJPA collection implementations. But I want to have my own collection implementation inside my entities.
E.g.: private Set<Item> items = new MyHashSet<Item>();
should be
I proved this statement by creating two Eclipse sample projects which you can find in the attachments of this ticket. This problem occures in both of the newest version of OpenJPA.
To execute the JUnit test go to src/openjpa/test/FailingTest.java and hit run. You will see an error displayed in the console. To get this test case green only openjpa.model.AbstractCategory has to be "unabstract". Just remove "abstract" in its class definition.
I hope my informations help you to fix this issue in a reasonable time.
unfinished scentence completed.
> Abstract entity causes standard openjpa collection proxies to be injected even if custom collections are used.
> --------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-2110
> URL: https://issues.apache.org/jira/browse/OPENJPA-2110
> Project: OpenJPA
> Issue Type: Bug
> Components: Enhance
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Labels: abstract,, collection, custom, project, proxy,, sample
>
> When using an abstract entity, all collections defined in this super class are incorrectly filled in with standard OpenJPA collection implementations. But I want to have my own collection implementation inside my entities.
> E.g.: private Set<Item> items = new MyHashSet<Item>();
> should be a specialized collection proxy, but when an abstract entity comes in only the standard OpenJPA collection proxy is used.
> I proved this statement by creating two Eclipse sample projects which you can find in the attachments of this ticket. This problem occures in both of the newest version of OpenJPA.
> To execute the JUnit test go to src/openjpa/test/FailingTest.java and hit run. You will see an error displayed in the console. To get this test case green only openjpa.model.AbstractCategory has to be "unabstract". Just remove "abstract" in its class definition.
> I hope my informations help you to fix this issue in a reasonable time.
--
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