You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2015/08/17 10:10:45 UTC
[jira] [Updated] (OPENJPA-2602) OracleDictionary uses reflection
way too often
[ https://issues.apache.org/jira/browse/OPENJPA-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg updated OPENJPA-2602:
-----------------------------------
Attachment: OPENJPA-2602.4review.patch
Plz review this patch. I've switched out dynamic Class.forName etc with ones evaluated in the ct. The reason I like this to get reviewed before I commit it is to check that I didn't mess up any ClassLoader stuff (classes not being available during ct but only later, etc)
> OracleDictionary uses reflection way too often
> ----------------------------------------------
>
> Key: OPENJPA-2602
> URL: https://issues.apache.org/jira/browse/OPENJPA-2602
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 2.4.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 2.4.1
>
> Attachments: OPENJPA-2602.4review.patch
>
>
> OracleDictionary has many Class.forName, getMethod and getField for oracle.jdbc.OraclePreparedStatement.
> This gets executed every time a setString gets used. Which can create quite some overhead.
> We might check those Members at construction time and use this info later at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)