openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (OPENJPA-542) OracleDictionary.getEmptyClob uses its classloader instead of the current classloader.
Date Thu, 17 Apr 2008 18:29:28 GMT

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

Michael Dick reassigned OPENJPA-542:
------------------------------------

    Assignee: Michael Dick

> OracleDictionary.getEmptyClob uses its classloader instead of the current classloader.

> ---------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-542
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-542
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.3, 1.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The OracleDictionary class calls Class.forName("oracle.sql.CLOB") and Class.forName("oracle.sql.BLOB")
to get the class objects for BLOBs and CLOBs. This approach uses the classloader which loaded
OracleDictionary, which might not have access to the Oracle JDBC classes ie if OpenJPA is
in a different OSGi bundle from the jdbc driver. 
> Instead we should get the current classloader which is more likely to contain the JDBC
driver classes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message