• java学习day23-JDBC-Class.forName("com.mysql.jdbc.Driver")


    Class.forName("com.mysql.jdbc.Driver") 的意义

    手动调用Class.forName()

    我们知道当我们连接MySQL数据库时,会使用如下代码:

     try {
            Class.forName("com.mysql.jdbc.Driver");
            connection = DriverManager.getConnection("jdbc:mysql:///jt_db", "root", 			"12345");
     } catch (Exception e) {
            e.printStackTrace();
     }
    

      那么Class.forName()有什么作用呢?

      首先我们知道Class.forName() 方法要求JVM查找并加载指定的类到内存中,此时将"com.mysql.jdbc.Driver" 当做参数传入,就是告诉JVM,去"com.mysql.jdbc"这个路径下找Driver类,将其加载到内存中。

    由于加载类文件时会执行其中的静态代码块,其中Driver类的源码如下

    public class Driver extends NonRegisteringDriver implements java.sql.Driver {
            public Driver() throws SQLException {
            }
            static {
                try {
                    DriverManager.registerDriver(new Driver());
                    //首先new一个Driver对象,并将它注册到DriverManage中
                } catch (SQLException var1) {
                    throw new RuntimeException("Can't register driver!");
                }
        	}
    }
    

    接下来我们再看看这个DriverManager.registerDriver 方法:

    public static synchronized void registerDriver(java.sql.Driver driver)
        throws SQLException {
    
        registerDriver(driver, null);
    }
    

     继续看这个registerDriver(driver, null) 方法

    private final static CopyOnWriteArrayList<DriverInfo> registeredDrivers = new CopyOnWriteArrayList<>();// registeredDrivers 是一个支持并发的arraylist
    ......
        public static void registerDriver(java.sql.Driver driver, DriverAction da)
        throws SQLException {
        if (driver != null) {
            //如果该驱动尚未注册,那么将他添加到 registeredDrivers 中去。这是一个支持并发情况的特殊ArrayList
            registeredDrivers.addIfAbsent(new DriverInfo(driver, da));
        } else {
            // This is for compatibility with the original DriverManager
            throw new NullPointerException();
        }
        println("registerDriver: " + driver);
    }
    

    此时,Class.forName(“com.mysql.jdbc.Driver”) 的工作就完成了,工作就是:将mysql驱动注册到DriverManager中去。接下来我们看是怎么进行调用的

    DriverManager.getConnection方法分析

    注册到DriverManager中之后,我们就可以通过DriverManager的getConnection方法获得mysql的连接了:

    Connection conn = DriverManager.getConnection("jdbc:mysql:///jt_db", "root", "1234");
    接下来我们在看看这个getConnection方法:

    @CallerSensitive
    public static Connection getConnection(String url,
        String user, String password) throws SQLException {
        ....
        return (getConnection(url, info, Reflection.getCallerClass()));
    }
    

    同样,调用了自身的 getConnection方法,继续往下看

    private static Connection getConnection(
        String url, java.util.Properties info, Class<?> caller) throws SQLException {
        ClassLoader callerCL = caller != null ? caller.getClassLoader() : null;
        synchronized(DriverManager.class) {
            // synchronize loading of the correct classloader.
            if (callerCL == null) {
                callerCL = Thread.currentThread().getContextClassLoader();
            }
        }
        // Walk through the loaded registeredDrivers attempting to make a connection.
        // Remember the first exception that gets raised so we can reraise it.
        SQLException reason = null;
    
        for(DriverInfo aDriver : registeredDrivers) {
            // If the caller does not have permission to load the driver then skip it.
            if(isDriverAllowed(aDriver.driver, callerCL)) {
                try {
                    Connection con = aDriver.driver.connect(url, info);
                    if (con != null) {
                        // Success!
                        return (con);
                    }
                } catch (SQLException ex) {
                    if (reason == null) {
                        reason = ex;
                    }
                }
            } else {
                println("skipping: " + aDriver.getClass().getName());
            }
        }
    
        // if we got here nobody could connect.
        if (reason != null)    {
            println("getConnection failed: " + reason);
            throw reason;
        }
        throw new SQLException("No suitable driver found for "+ url, "08001");
    }
    

    可以看到它对上文提到的静态变量 registeredDrivers 进行了遍历,调用了connect(url, info)方法,这是一个接口,由各个不同的驱动自己实现。

    /**
         * Attempts to make a database connection to the given URL.
         * The driver should return "null" if it realizes it is the wrong kind
         * of driver to connect to the given URL.  This will be common, as when
         * the JDBC driver manager is asked to connect to a given URL it passes
         * the URL to each loaded driver in turn.
         */
    Connection connect(String url, java.util.Properties info)
        throws SQLException;
    

    到此为止,我们就获得了connection对象,现在就可以对数据库进行操作了。

    不手动注册驱动也能使用JDBC [ 去除class.forName ]

    在高版本的JDK,已经不需要手动调用class.forName方法了,在DriverManager的源码中可以看到一个静态块

    /**
         * Load the initial JDBC drivers by checking the System property
         * jdbc.properties and then use the {@code ServiceLoader} mechanism
         */
    static {
        loadInitialDrivers();
        println("JDBC DriverManager initialized");
    }
    

    进入loadInitialDrivers()方法中看到以下一段代码:

    private static void loadInitialDrivers() {
        String drivers;
        try {
            drivers = AccessController.doPrivileged(new PrivilegedAction<String>() {
                public String run() {
                    return System.getProperty("jdbc.drivers");
                }
            });
        } catch (Exception ex) {
            drivers = null;
        }
        // If the driver is packaged as a Service Provider, load it.
        // Get all the drivers through the classloader
        // exposed as a java.sql.Driver.class service.
        // ServiceLoader.load() replaces the sun.misc.Providers()
    
        AccessController.doPrivileged(new PrivilegedAction<Void>() {
            public Void run() {
    
                ServiceLoader<Driver> loadedDrivers = ServiceLoader.load(Driver.class);
                Iterator<Driver> driversIterator = loadedDrivers.iterator();
    
                /* Load these drivers, so that they can be instantiated.
                     * It may be the case that the driver class may not be there
                     * i.e. there may be a packaged driver with the service class
                     * as implementation of java.sql.Driver but the actual class
                     * may be missing. In that case a java.util.ServiceConfigurationError
                     * will be thrown at runtime by the VM trying to locate
                     * and load the service.
                     *
                     * Adding a try catch block to catch those runtime errors
                     * if driver not available in classpath but it's
                     * packaged as service and that service is there in classpath.
                     */
                try{
                    while(driversIterator.hasNext()) {
                        driversIterator.next();
                    }
                } catch(Throwable t) {
                    // Do nothing
                }
                return null;
            }
        });
    

    重点是第20行,ServiceLoader.load(Driver.class)

    上面这行代码可以把类路径下所有jar包中META-INF/services/java.sql.Driver文件中定义的类加载上来,此类必须继承自java.sql.Driver。

    最后我们看一下第37行最后我们看一下Iterator的next()方法做了什么就完全懂了,通过next()方法调用了:

    private S nextService() {
        if (!hasNextService())
            throw new NoSuchElementException();
        String cn = nextName;
        nextName = null;
        Class<?> c = null;
        try {
            c = Class.forName(cn, false, loader); //看这里,Class.forName()
        } catch (ClassNotFoundException x) {
            fail(service,
                 "Provider " + cn + " not found");
       }
        if (!service.isAssignableFrom(c)) {
           fail(service,
                 "Provider " + cn  + " not a subtype");
        }
        try {
            S p = service.cast(c.newInstance());
            providers.put(cn, p);
            return p;
        } catch (Throwable x) {
            fail(service,
                 "Provider " + cn + " could not be instantiated",
                x);
        }
        throw new Error();          // This cannot happen
    }
    
  • 相关阅读:
    东南亚“美团” Grab 的搜索索引优化之法
    linux中init.d文件夹的说明
    缓存踩踏:Facebook 史上最严重的宕机事件分析
    burp suite
    千万实例可观测采集器iLogtail
    grep 匹配多个关键字
    127.0.0.1和0.0.0.0
    Python 爬虫进阶必备 | 某常见 cookie 加密算法逻辑分析 (加速乐 jsl) https://mp.weixin.qq.com/s/fKuPs2b3MvOi8y4hPVbgNA
    百度商业大规模高性能全息日志检索技术揭秘
    ECB加密 CBC
  • 原文地址:https://www.cnblogs.com/liqbk/p/13027389.html
Copyright © 2020-2023  润新知