[OPENJPA-2087] Remove or limit the use of the ConcreteClassGenerator

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Component/s: build / infrastructure
• Patch Info: Patch Available
• Assignee: Kevin W. Sutter
• Reporter: Jacob Nowosatka
• Created: 05/Dec/11 23:28
• Updated: 09/Mar/12 21:58
• Resolved: 03/Jan/12 20:13

Description

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

Issue Links

• breaks: OPENJPA-2153 NoSuchMethodException of DBCPDriverDataSource.newInstance()
• is related to: OPENJPA-1520 Move trunk (2.0.x) to require Java 6 to build (but target 1.5 runtime)
• is related to: OPENJPA-1792 Drop JDK5 support starting with OpenJPA 2.1