[OPENJPA-2110] Abstract entity causes standard openjpa collection proxies to be injected even if custom collections are used.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2, 2.1.1
• Fix Version/s: 2.3.0
• Component/s: kernel
• Labels: abstract, collection custom project proxy, sample
• Environment: Java SE 1.6
• Assignee: Richard G. Curtis
• Reporter: Johannes Leimer
• Created: 17/Jan/12 20:04
• Updated: 11/Apr/12 14:27
• Resolved: 11/Apr/12 13:42

Description

When using an abstract entity, all collections defined in this super class are incorrectly filled in with standard OpenJPA collection implementations. I'd like 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.