Mybatis源码分析三

我们在使用 Mybatis 获取到 SqlSession 之后要想进行数据库操作，首先要做的工作就是获取到对应的 Mapper ，如：AuthorMapper mapper = session.getMapper(AuthorMapper.class);
从上一篇文章 Mybatis源码分析二 我们知道，SqlSession 的实现类 DefaultSqlSession 中有一个 Configuration 类型的成员变量，该 configuration 可以获取 Mapper：

  @Override
  public <T> T getMapper(Class<T> type) {
    return configuration.<T>getMapper(type, this);
  }

继续进入 org.apache.ibatis.session.Configuration 类可以看到其实现：

  public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
    return mapperRegistry.getMapper(type, sqlSession);
  }

再往下走进入 org.apache.ibatis.binding.MapperRegistry 类：

  public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
    final MapperProxyFactory<T> mapperProxyFactory = (MapperProxyFactory<T>) knownMappers.get(type);
    if (mapperProxyFactory == null) {
      throw new BindingException("Type " + type + " is not known to the MapperRegistry.");
    }
    try {
      return mapperProxyFactory.newInstance(sqlSession);
    } catch (Exception e) {
      throw new BindingException("Error getting mapper instance. Cause: " + e, e);
    }
  }

注意 mapperProxyFactory.newInstance(sqlSession);这行代码，跟进去可以看到：

  @SuppressWarnings("unchecked")
  protected T newInstance(MapperProxy<T> mapperProxy) {
    return (T) Proxy.newProxyInstance(mapperInterface.getClassLoader(), new Class[] { mapperInterface }, mapperProxy);
  }

  public T newInstance(SqlSession sqlSession) {
    final MapperProxy<T> mapperProxy = new MapperProxy<T>(sqlSession, mapperInterface, methodCache);
    return newInstance(mapperProxy);
  }

到这里我想大家已经明白了，原来 MyBatis 获取 Mapper 实例采用的方式是：动态代理。动态代理类就是 MapperProxy 类。