You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2008/03/24 19:15:24 UTC
[jira] Created: (OPENJPA-542) OracleDictionary.getEmptyClob uses
its classloader instead of the current classloader.
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.2, 1.0.1, 1.0.0
Reporter: Michael Dick
Fix For: 1.0.3, 1.1.0
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.
[jira] Assigned: (OPENJPA-542) OracleDictionary.getEmptyClob uses
its classloader instead of the current classloader.
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (OPENJPA-542) OracleDictionary.getEmptyClob uses its
classloader instead of the current classloader.
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick closed OPENJPA-542.
--------------------------------
Resolution: Fixed
> 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
> 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.