You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/21 11:11:00 UTC
[jira] [Updated] (IGNITE-5408) JDBC driver should not require
Class.forName() call
[ https://issues.apache.org/jira/browse/IGNITE-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-5408:
------------------------------------
Component/s: (was: sql)
jdbc
> JDBC driver should not require Class.forName() call
> ---------------------------------------------------
>
> Key: IGNITE-5408
> URL: https://issues.apache.org/jira/browse/IGNITE-5408
> Project: Ignite
> Issue Type: Task
> Components: jdbc
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Modern JDBC drivers do not require explicit init through {{Class.forName}}. Instead, it works as follows:
> 1) {{java.sql.Driver}} file is created under {{META-INF/services}} directory.
> 2) Driver has static initializer which registers itself within {{DriverManager}}.
> We should do that for both think and new thin drivers, and remove all {{Class.forName}} calls from tests afterwards.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)