[
https://issues.apache.org/jira/browse/JCR-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249230#comment-13249230
]
Justin Edelson edited comment on JCR-3288 at 4/7/12 12:15 PM:
--------------------------------------------------------------
Wouldn't ConnectionFactory.class.getClassLoader() be a better way of obtaining
the correct classloader?
was (Author: justinedelson):
Wouldn't ConnectionFactory.getClassLoader() be a better way of obtaining
the correct classloader?
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
