You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Albert Lee (Closed) (JIRA)" <ji...@apache.org> on 2012/02/02 18:20:54 UTC

[jira] [Closed] (OPENJPA-2087) Remove or limit the use of the ConcreteClassGenerator

     [ https://issues.apache.org/jira/browse/OPENJPA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Albert Lee closed OPENJPA-2087.
-------------------------------


Close issue in preparation for 2.2.0 release.
                
> Remove or limit the use of the ConcreteClassGenerator
> -----------------------------------------------------
>
>                 Key: OPENJPA-2087
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2087
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>            Reporter: Jacob Nowosatka
>            Assignee: Kevin Sutter
>            Priority: Minor
>             Fix For: 2.2.0
>
>         Attachments: OPENJPA-2087-1.patch, OPENJPA-2087-2.patch
>
>
> Now that we have to only support Java 6 in OpenJPA 2.x, there is discussion about revisiting the issue of removing or limiting the use of the ConcreteClassGenerator. This was originally discussed in OpenJPA-1520 [1].  This would help cleanup some of the code and would hopefully result in some performance gains, despite that it didn't seem to help with earlier primitive tests.
> [1] https://issues.apache.org/jira/browse/OPENJPA-1520

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