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 (Created) (JIRA)" <ji...@apache.org> on 2012/01/17 21:05:39 UTC
[jira] [Created] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
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: 2.1.1, 1.2.2
Environment: Java SE 1.6
Reporter: Johannes Leimer
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.
--
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] [Closed] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Leimer closed OPENJPA-2110.
------------------------------------
verified test case
> 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: kernel
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Fix For: 2.3.0
>
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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] [Resolved] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Rick Curtis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis resolved OPENJPA-2110.
----------------------------------
Resolution: Fixed
Johannes --
Thanks for the complete testcase! Sorry about taking so long to fix this one.
Thanks,
Rick
> 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: kernel
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Fix For: 2.3.0
>
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org>.
[ 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. 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.
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 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.
> 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
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Rick Curtis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis updated OPENJPA-2110:
---------------------------------
Component/s: (was: Enhance)
kernel
Fix Version/s: 2.3.0
> 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: kernel
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Fix For: 2.3.0
>
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Leimer updated OPENJPA-2110:
-------------------------------------
Attachment: openjpa.2.1.1.proxybug.zip
openjpa.1.2.2.proxybug.zip
The sample projects mentioned above.
> 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
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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
[jira] [Commented] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Rick Curtis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251562#comment-13251562 ]
Rick Curtis commented on OPENJPA-2110:
--------------------------------------
ommitted testcase and code fix to trunk at revision 1324759.
> 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: kernel
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Fix For: 2.3.0
>
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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] [Assigned] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Rick Curtis (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis reassigned OPENJPA-2110:
------------------------------------
Assignee: Rick Curtis
> 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
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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] [Commented] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251621#comment-13251621 ]
Johannes Leimer commented on OPENJPA-2110:
------------------------------------------
Great job Rick.
Thank you for your time.
I think it's good manner to provide a test case. TDD for the win :-)
Anyway, thank you for your acknowledgment.
Kind Regards,
Johannes
> 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: kernel
> Affects Versions: 1.2.2, 2.1.1
> Environment: Java SE 1.6
> Reporter: Johannes Leimer
> Assignee: Rick Curtis
> Labels: abstract,, collection, custom, project, proxy,, sample
> Fix For: 2.3.0
>
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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.
--
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-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Leimer updated OPENJPA-2110:
-------------------------------------
Comment: was deleted
(was: 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
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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
[jira] [Updated] (OPENJPA-2110) Abstract entity causes standard
openjpa collection proxies to be injected even if custom collections are
used.
Posted by "Johannes Leimer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Leimer updated OPENJPA-2110:
-------------------------------------
Comment: was deleted
(was: The sample projects mentioned above.)
> 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
> Attachments: openjpa.1.2.2.proxybug.zip, openjpa.2.1.1.proxybug.zip
>
>
> 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