You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/12/22 05:00:08 UTC
[jira] [Resolved] (JCR-3288) ConnectionFactory.getDriverClass()
should use Thread.currentThread().getContextClassLoader(); instead of
Class.forName()
[ https://issues.apache.org/jira/browse/JCR-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3288.
---------------------------------
Resolution: Not A Bug
> ConnectionFactory.getDriverClass() should use Thread.currentThread().getContextClassLoader(); instead of Class.forName()
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3288
> URL: https://issues.apache.org/jira/browse/JCR-3288
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.3.3
> Environment: WXP Sun JDK 1.6.0_30 Derby database
> Reporter: Francis ANDRE
> Priority: Critical
>
> Hi
> The ConnectionFactory.getDriverClass() should use Thread.currentThread().getContextClassLoader(); instead of Class.forName() otherwise dynamically added jdbc drivers to the classpath are not found;
> ClassLoader cl = Thread.currentThread().getContextClassLoader();
> return cl.loadClass(driver);
> // return Class.forName(driver);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)