6.MyBatis解析和运行大致原理流程

作者: 落叶飞逝的恋 | 来源:发表于2017-08-29 21:10 被阅读83次

6.MyBatis解析和运行大致原理流程
NALU格式
ReactNative IOS 运行原理之
spring 5.0.x源码学习系列二: 从Annotation
vue核心之虚拟DOM(vdom)
vue核心之虚拟DOM(vdom)
mybatis的解析和运行原理
云原生|Kubernetes技术架构
RunLoop 理解
热修&插件 - Dalvik加载Dex相关流程

1.前言

首先要理解MyBatis的运行原理，首先第一个需要掌握的是代理模式。因为之前的一些文章里面，我们写的案例，里面都有申明dao层的接口。我们只是定义了一系列接口定义，而并没有实现其逻辑接口。而这些都是MyBatis使用了代理模式帮我们实现了。

补充下：了解代理模式看我之前的一篇关于代理模式的博文

代理模式 (Proxy)

2.构建SqlSessionFactory过程

SqlSessionFactory创建流程

SqlSessionFactory是MyBatis的核心，主要提供SqlSession。而SqlSessionFactory是采用生成器模式又称构建者模式生成。

public static SqlSessionFactory buildSqlSessionFactory() throws IOException {
    InputStream inputStream = Resources.getResourceAsStream("config/mybatis-config.xml");
    return new SqlSessionFactoryBuilder().build(inputStream);
}

2.1SqlSessionFactory构建步骤

1.使用org.apache.ibatis.builder.xml.XMLConfigBuilder去解析配置xml属性，并将解析的内容存放在org.apache.ibatis.session.Configuration中
2.使用Configuration对象去创建SqlSessionFactory。因为SqlSessionFactory是接口，所以MyBatis内置了默认的SqlSessionFactory实现类DefaultSqlSessionFactory

使用建造者模式的好处就是将生成SqlSessionFactory的过程与xml解析的过程分割开来，这样便于代码维护。

2.2构建Configuration

org.apache.ibatis.builder.xml.XMLConfigBuilder重要的两个方法

public Configuration parse() {
    if (parsed) {
      throw new BuilderException("Each XMLConfigBuilder can only be used once.");
    }
    parsed = true;
    parseConfiguration(parser.evalNode("/configuration"));
    return configuration;
  }

private void parseConfiguration(XNode root) {
    try {
      //issue #117 read properties first
      propertiesElement(root.evalNode("properties"));
      Properties settings = settingsAsProperties(root.evalNode("settings"));
      loadCustomVfs(settings);
      typeAliasesElement(root.evalNode("typeAliases"));
      pluginElement(root.evalNode("plugins"));
      objectFactoryElement(root.evalNode("objectFactory"));
      objectWrapperFactoryElement(root.evalNode("objectWrapperFactory"));
      reflectorFactoryElement(root.evalNode("reflectorFactory"));
      settingsElement(settings);
      // read it after objectFactory and objectWrapperFactory issue #631
      environmentsElement(root.evalNode("environments"));
      databaseIdProviderElement(root.evalNode("databaseIdProvider"));
      typeHandlerElement(root.evalNode("typeHandlers"));
      mapperElement(root.evalNode("mappers"));
    } catch (Exception e) {
      throw new BuilderException("Error parsing SQL Mapper Configuration. Cause: " + e, e);
    }
  }

3.SqlSession运行过程

SqlSession是获取Mapper的重要接口。

因为上面获取的是DefaultSqlSessionFactory，所以使用到的是DefaultSqlSession

3.1 Mapper映射器使用动态代理

package org.apache.ibatis.binding.MapperProxyFactory

@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);
}

MapperProxy实现java.lang.reflect.InvocationHandler

 @Override
  public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
    try {
      if (Object.class.equals(method.getDeclaringClass())) {
        return method.invoke(this, args);
      } else if (isDefaultMethod(method)) {
        return invokeDefaultMethod(proxy, method, args);
      }
    } catch (Throwable t) {
      throw ExceptionUtil.unwrapThrowable(t);
    }
    final MapperMethod mapperMethod = cachedMapperMethod(method);
    return mapperMethod.execute(sqlSession, args);
  }

4.SqlSession的重要对象

1.Executor（执行器对象）

由它来调度StatementHandler、ParameterHandler、ResultHandler等来执行对应的SQL

2.StatementHandler（数据库会话器）

它的作用是使用数据库的Statement（PreparedStatemnet）执行操作，它是四大对象的核心，起到承上启下的作用。

3.ParameterHandler（参数处理器）

用于SQL对参数的处理

4.ResultHandler（结果处理器）

是进行最后数据集（ResultSet）的封装返回

4.1Executor

Executor是我们在创建好SqlSessionFactory之后，使用factory.openSession()进行创建。在MyBatis存在三种执行器。

1.simple。简易执行器，不配置就是默认的执行器

2.resuse。是一种执行器重用预处理语句

3.batch。执行器重用语句和批量更新，它是针对批量专用的执行器

openSession

 @Override
  public SqlSession openSession() {
    return openSessionFromDataSource(configuration.getDefaultExecutorType(), null, false);
  }

上面获取的getDefaultExecutorType是protected ExecutorType defaultExecutorType = ExecutorType.SIMPLE;如果没有设置执行器的类型的话是simple

openSessionFromDataSource

 private SqlSession openSessionFromDataSource(ExecutorType execType, TransactionIsolationLevel level, boolean autoCommit) {
    Transaction tx = null;
    try {
      final Environment environment = configuration.getEnvironment();
      final TransactionFactory transactionFactory = getTransactionFactoryFromEnvironment(environment);
      tx = transactionFactory.newTransaction(environment.getDataSource(), level, autoCommit);
      final Executor executor = configuration.newExecutor(tx, execType);
      return new DefaultSqlSession(configuration, executor, autoCommit);
    } catch (Exception e) {
      closeTransaction(tx); // may have fetched a connection so lets call close()
      throw ExceptionFactory.wrapException("Error opening session.  Cause: " + e, e);
    } finally {
      ErrorContext.instance().reset();
    }
  }

newExecutor

public Executor newExecutor(Transaction transaction, ExecutorType executorType) {
    executorType = executorType == null ? defaultExecutorType : executorType;
    executorType = executorType == null ? ExecutorType.SIMPLE : executorType;
    Executor executor;
    if (ExecutorType.BATCH == executorType) {
      executor = new BatchExecutor(this, transaction);
    } else if (ExecutorType.REUSE == executorType) {
      executor = new ReuseExecutor(this, transaction);
    } else {
      executor = new SimpleExecutor(this, transaction);
    }
    if (cacheEnabled) {
      executor = new CachingExecutor(executor);
    }
    executor = (Executor) interceptorChain.pluginAll(executor);
    return executor;
  }

SimpleExecutor内部实现

  @Override
  public <E> List<E> doQuery(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, BoundSql boundSql) throws SQLException {
    Statement stmt = null;
    try {
      Configuration configuration = ms.getConfiguration();
      StatementHandler handler = configuration.newStatementHandler(wrapper, ms, parameter, rowBounds, resultHandler, boundSql);
      stmt = prepareStatement(handler, ms.getStatementLog());
      return handler.<E>query(stmt, resultHandler);
    } finally {
      closeStatement(stmt);
    }
  }

  private Statement prepareStatement(StatementHandler handler, Log statementLog) throws SQLException {
    Statement stmt;
    Connection connection = getConnection(statementLog);
    stmt = handler.prepare(connection, transaction.getTimeout());
    handler.parameterize(stmt);
    return stmt;
  }

MyBatis根据Configuration来构建StatementHandler，然后使用prepareStatement，对SQL编译并对参数进行初始化。

实现过程：

1.调用StatementHandler的prepare进行预编译和基础设置
2.调用StatementHandler的parameterize来设置参数并执行
3.利用ResultSetHandler组装查询结果给调用者完成一次查询

4.2StatementHandler（数据库会话器）

数据库会话器是专门处理数据库会话的

创建StatementHandler实例

在包中org.apache.ibatis.session.Configuration

 public StatementHandler newStatementHandler(Executor executor, MappedStatement mappedStatement, Object parameterObject, RowBounds rowBounds, ResultHandler resultHandler, BoundSql boundSql) {
    StatementHandler statementHandler = new RoutingStatementHandler(executor, mappedStatement, parameterObject, rowBounds, resultHandler, boundSql);
    statementHandler = (StatementHandler) interceptorChain.pluginAll(statementHandler);
    return statementHandler;
  }

RoutingStatementHandler并不是一个真实的服务对象，其代码只是做一个简单工厂的职责，使用方式不太好。

 public RoutingStatementHandler(Executor executor, MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, BoundSql boundSql) {

    switch (ms.getStatementType()) {
      case STATEMENT:
        delegate = new SimpleStatementHandler(executor, ms, parameter, rowBounds, resultHandler, boundSql);
        break;
      case PREPARED:
        delegate = new PreparedStatementHandler(executor, ms, parameter, rowBounds, resultHandler, boundSql);
        break;
      case CALLABLE:
        delegate = new CallableStatementHandler(executor, ms, parameter, rowBounds, resultHandler, boundSql);
        break;
      default:
        throw new ExecutorException("Unknown statement type: " + ms.getStatementType());
    }

  }

常用的PreparedStatementHandler

PreparedStatementHandler是继承BaseStatementHandler

  @Override
  public Statement prepare(Connection connection, Integer transactionTimeout) throws SQLException {
    ErrorContext.instance().sql(boundSql.getSql());
    Statement statement = null;
    try {
      statement = instantiateStatement(connection);
      setStatementTimeout(statement, transactionTimeout);
      setFetchSize(statement);
      return statement;
    } catch (SQLException e) {
      closeStatement(statement);
      throw e;
    } catch (Exception e) {
      closeStatement(statement);
      throw new ExecutorException("Error preparing statement.  Cause: " + e, e);
    }
  }

 @Override
  protected Statement instantiateStatement(Connection connection) throws SQLException {
    String sql = boundSql.getSql();
    if (mappedStatement.getKeyGenerator() instanceof Jdbc3KeyGenerator) {
      String[] keyColumnNames = mappedStatement.getKeyColumns();
      if (keyColumnNames == null) {
        return connection.prepareStatement(sql, PreparedStatement.RETURN_GENERATED_KEYS);
      } else {
        return connection.prepareStatement(sql, keyColumnNames);
      }
    } else if (mappedStatement.getResultSetType() != null) {
      return connection.prepareStatement(sql, mappedStatement.getResultSetType().getValue(), ResultSet.CONCUR_READ_ONLY);
    } else {
      return connection.prepareStatement(sql);
    }
  }

4.3 ParameterHandler

设置SQL参数。handler.parameterize(stmt);

  public void parameterize(Statement statement) throws SQLException {
    parameterHandler.setParameters((PreparedStatement) statement);
  }

设置参数是使用的DefaultParameterHandler

  @Override
  public void setParameters(PreparedStatement ps) {
    ErrorContext.instance().activity("setting parameters").object(mappedStatement.getParameterMap().getId());
    List<ParameterMapping> parameterMappings = boundSql.getParameterMappings();
    if (parameterMappings != null) {
      for (int i = 0; i < parameterMappings.size(); i++) {
        ParameterMapping parameterMapping = parameterMappings.get(i);
        if (parameterMapping.getMode() != ParameterMode.OUT) {
          Object value;
          String propertyName = parameterMapping.getProperty();
          if (boundSql.hasAdditionalParameter(propertyName)) { // issue #448 ask first for additional params
            value = boundSql.getAdditionalParameter(propertyName);
          } else if (parameterObject == null) {
            value = null;
          } else if (typeHandlerRegistry.hasTypeHandler(parameterObject.getClass())) {
            value = parameterObject;
          } else {
            MetaObject metaObject = configuration.newMetaObject(parameterObject);
            value = metaObject.getValue(propertyName);
          }
          TypeHandler typeHandler = parameterMapping.getTypeHandler();
          JdbcType jdbcType = parameterMapping.getJdbcType();
          if (value == null && jdbcType == null) {
            jdbcType = configuration.getJdbcTypeForNull();
          }
          try {
            typeHandler.setParameter(ps, i + 1, value, jdbcType);
          } catch (TypeException e) {
            throw new TypeException("Could not set parameters for mapping: " + parameterMapping + ". Cause: " + e, e);
          } catch (SQLException e) {
            throw new TypeException("Could not set parameters for mapping: " + parameterMapping + ". Cause: " + e, e);
          }
        }
      }
    }
  }

4.4ResultSetHandler

用于组装数据返回的结果集到对应的POJO上

public interface ResultSetHandler {

  <E> List<E> handleResultSets(Statement stmt) throws SQLException;

  <E> Cursor<E> handleCursorResultSets(Statement stmt) throws SQLException;

  void handleOutputParameters(CallableStatement cs) throws SQLException;

}

宏观的看，MyBatis的整理架构图如下：

MyBatis整体架构图

6.MyBatis解析和运行大致原理流程
1.前言首先要理解MyBatis的运行原理，首先第一个需要掌握的是代理模式。因为之前的一些文章里面，我们写的案例...
NALU格式
音视频编码在流媒体和网络领域占有重要地位；流媒体编解码流程大致如下图所示： x264原理解析参考链接： x264...
ReactNative IOS 运行原理之
上一期我们介绍ReactNative IOS 运行原理之的大致运行原理，这一期...
spring 5.0.x源码学习系列二: 从Annotation
揭开AnnotationConfigApplicationContext类运行的神秘面纱一、运行大致流程图在这里...
vue核心之虚拟DOM(vdom)
一、真实DOM和其解析流程？浏览器渲染引擎工作流程都差不多，大致分为5步，创建DOM树——创建StyleRu...
vue核心之虚拟DOM(vdom)
一、真实DOM和其解析流程？浏览器渲染引擎工作流程都差不多，大致分为5步，创建DOM树——创建StyleRule...
mybatis的解析和运行原理
一、mybatis的运行分为两大部分 1、读取配置文件到缓存到configuration对象，用以创建SqlSes...
云原生|Kubernetes技术架构
01：容器运行时技术深度剖析 1.1 容器引擎和运行时机制原理解析 kubernetes定义的容器运行时接口：CR...
RunLoop 理解
Runloop解析概述从字面的意思来看，就是运行循环，没有终点，一直运行。下面先看下大致 runloop 运行...
热修&插件 - Dalvik加载Dex相关流程
一、Dalvik整体类加载过程大致流程与Art基本相同。只是具体dex优化流程、解析加载流程区别会比较大。二、...

6.MyBatis解析和运行大致原理流程

1.前言

2.构建SqlSessionFactory过程

2.1SqlSessionFactory构建步骤

2.2构建Configuration

3.SqlSession运行过程

3.1 Mapper映射器使用动态代理

4.SqlSession的重要对象

4.1Executor

4.2StatementHandler（数据库会话器）

4.3 ParameterHandler

4.4ResultSetHandler

相关文章

6.MyBatis解析和运行大致原理流程

NALU格式

ReactNative IOS 运行原理之

spring 5.0.x源码学习系列二: 从Annotation

vue核心之虚拟DOM(vdom)

vue核心之虚拟DOM(vdom)

mybatis的解析和运行原理

云原生|Kubernetes技术架构

RunLoop 理解

热修&插件 - Dalvik加载Dex相关流程

网友评论

延伸阅读

深度阅读

栏目导航

热点阅读

测试开发栈

程序员