mybatis部分源码

mybatis源码

初始化的时候读取配置

获得一个SqlsessionFactory

 //读取配置文件成流
InputStream inputStream = Resources.getResourceAsStream("mybatis-config.xml"); 
//解析配置文件流,获得一个SqlsessionFactory
SqlSessionFactory factory = new SqlSessionFactoryBuilder().build(inputStream);

进入new SqlSessionFactoryBuilder().build(inputStream)方法

// 1.上面调用的这个方法
public SqlSessionFactory build(InputStream inputStream) {
	//在这里调用重载的方法
	return build(inputStream, null, null);
}
// 2.所以实际调用的是这个方法
public SqlSessionFactory build(InputStream inputStream, String environment, Properties properties) {
	try {
		// XMLConfigBuilder是专门解析mybatis的配置文件的类
		XMLConfigBuilder parser = new XMLConfigBuilder(inputStream, environment, properties);
		//parser.parse()返回了一个Configuration对象
		return build(parser.parse()); 
	} catch (Exception e) {
		throw ExceptionFactory.wrapException("Error building SqlSession.", e)
	}
}
//3.上面的return build(parser.parse())调用的是这个方法返回一个DefaultSqlSessionFactory
public SqlSessionFactory build(Configuration config) {
   return new DefaultSqlSessionFactory(config);
}

进入parser.parse()方法(org.apache.ibatis.builder.xml.XMLConfigBuilder#parse)

//先看看XMLConfigBuilder的构造方法
private XMLConfigBuilder(XPathParser parser, String environment, Properties props) {
    super(new Configuration());
    ErrorContext.instance().resource("SQL Mapper Configuration");
    this.configuration.setVariables(props);
    this.parsed = false;
    this.environment = environment;
    this.parser = parser;
  }

public Configuration parse() {
	//构造方法中被初始化成false
    if (parsed) {
      throw new BuilderException("Each XMLConfigBuilder can only be used once.");
    }
    parsed = true;
    //解析mybatis xml配置文件中的configuration标签
    parseConfiguration(parser.evalNode("/configuration"));
    return configuration;
  }
//解析xml
private void parseConfiguration(XNode root) {
    try {
      //解析<properties><properties/> 标签
      propertiesElement(root.evalNode("properties"));
      //解析<setting><setting/>标签
      Properties settings = settingsAsProperties(root.evalNode("settings"));
      //加载setting中自定义的vfs实现类
      loadCustomVfs(settings);
      //解析<typeAliases><typeAliases/> 标签 下面都是类似的功能
      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"));
      //跟一下源码,最终解析后都会调用configuration.addMappedStatement(statement);
      //mapperElement方法会分别解析mappers标签的子标签,根据他的子标签是Package、resource、url、class来执行逻辑
      mapperElement(root.evalNode("mappers"));
    } catch (Exception e) {
      throw new BuilderException("Error parsing SQL Mapper Configuration. Cause: " + e, e);
    }
  }
执行sql的时候
	//首先从DefaultSqlsession类中获得sqlsession  
	 SqlSession sqlSession = factory.openSession();
	 //然后执行sql  namespace是类的全限定名+方法名
	 List<User> list = sqlSession.selectList("com.mapper.UserMapper.getUserByName");

进入DefaultSqlSessionFactory类

  @Override
  public SqlSession openSession() {
  	//configuration.getDefaultExecutorType()传入的类型是ExecutorType.SIMPLE
    return openSessionFromDataSource(configuration.getDefaultExecutorType(), null, false);
  }
/// /ExecutorType为Executor的类型, TransactionIsolationLevel为事务隔离级别,autoCommit是否开启事务
//openSession的多个重载方法可以指定获得的SeqSession的Executor类型和事务的处理
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);
      //根据类型创建executor
      final Executor executor = configuration.newExecutor(tx, execType);
      //这个方法获得一个defaultSqlSession
      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();
    }
  }

进入DefaultSqlSession类

  //重载方法调用
  @Override
  public <E> List<E> selectList(String statement) {
    return this.selectList(statement, null);
  }
  @Override
  public <E> List<E> selectList(String statement, Object parameter) {
    return this.selectList(statement, parameter, RowBounds.DEFAULT);
  }
  @Override
  public <E> List<E> selectList(String statement, Object parameter, RowBounds rowBounds) {
    try {
      //根据传入的全限定名+方法名从映射的Map中取出MappedStatement对象
      //之前解析配置类的时候,已经从xml文件解析放到了Configuration中了→configuration.addMappedStatement(statement);
      MappedStatement ms = configuration.getMappedStatement(statement);
      //调用执行器方法,rowBounds是用来逻辑分页,wrapCollection(parameter)是用来装饰集合或者数组参数,ResultHandler NO_RESULT_HANDLER = null;
      return executor.query(ms, wrapCollection(parameter), rowBounds, Executor.NO_RESULT_HANDLER);
    } catch (Exception e) {
      throw ExceptionFactory.wrapException("Error querying database.  Cause: " + e, e);
    } finally {
      ErrorContext.instance().reset();
    }
  }

进入BaseExecutor

@Override
  public <E> List<E> query(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler) throws SQLException {
  	//这里根据参数解析动态sql返回boundsql
    BoundSql boundSql = ms.getBoundSql(parameter);
    //查询缓存key
    CacheKey key = createCacheKey(ms, parameter, rowBounds, boundSql);
    return query(ms, parameter, rowBounds, resultHandler, key, boundSql);
 }

进入MappedStatement

public BoundSql getBoundSql(Object parameterObject) {
	//DynamicSqlSource的getBoundSql会解析动态sql<if><foreach>标签等,并把参数放进一个map
    BoundSql boundSql = sqlSource.getBoundSql(parameterObject);
    List<ParameterMapping> parameterMappings = boundSql.getParameterMappings();
    //如果没有参数则new一个boundsql
    if (parameterMappings == null || parameterMappings.isEmpty()) {
      boundSql = new BoundSql(configuration, boundSql.getSql(), parameterMap.getParameterMappings(), parameterObject);
    }

    // check for nested result maps in parameter mappings (issue #30)
    for (ParameterMapping pm : boundSql.getParameterMappings()) {
      String rmId = pm.getResultMapId();
      if (rmId != null) {
        ResultMap rm = configuration.getResultMap(rmId);
        if (rm != null) {
          hasNestedResultMaps |= rm.hasNestedResultMaps();
        }
      }
    }

    return boundSql;
  }

回到BaseExecutor

@Override
  public <E> List<E> query(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, CacheKey key, BoundSql boundSql) throws SQLException {
    ErrorContext.instance().resource(ms.getResource()).activity("executing a query").object(ms.getId());
    if (closed) {
      throw new ExecutorException("Executor was closed.");
    }
    if (queryStack == 0 && ms.isFlushCacheRequired()) {
      clearLocalCache();
    }
    List<E> list;
    try {
      queryStack++;
      //先从缓存里面拿
      list = resultHandler == null ? (List<E>) localCache.getObject(key) : null;
      if (list != null) {
      	//缓存里面有,处理存储过程的参数,因为存储过程可能有多个出参
        handleLocallyCachedOutputParameters(ms, key, parameter, boundSql);
      } else {
      	//从数据库里面拿
        list = queryFromDatabase(ms, parameter, rowBounds, resultHandler, key, boundSql);
      }
    } finally {
      queryStack--;
    }
    if (queryStack == 0) {
      for (DeferredLoad deferredLoad : deferredLoads) {
        deferredLoad.load();
      }
      // issue #601
      deferredLoads.clear();
      if (configuration.getLocalCacheScope() == LocalCacheScope.STATEMENT) {
        // issue #482
        clearLocalCache();
      }
    }
    return list;
  }
  
private <E> List<E> queryFromDatabase(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, CacheKey key, BoundSql boundSql) throws SQLException {
    List<E> list;
    //这里放一个占位符,其他查询进来的时候告诉它这个查询已经有线程在处理了
    localCache.putObject(key, EXECUTION_PLACEHOLDER);
    try {
      //查询
      list = doQuery(ms, parameter, rowBounds, resultHandler, boundSql);
    } finally {
      //万一报错,移除占位
      localCache.removeObject(key);
    }
    //查询结果加入缓存
    localCache.putObject(key, list);
    //如果statement是一个存储过程,把结果放进出参缓存
    if (ms.getStatementType() == StatementType.CALLABLE) {
      localOutputParameterCache.putObject(key, parameter);
    }
    return list;
  }

进入BaseExecutor的子类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();
      //传入参数创建StatementHanlder对象来执行查询
      StatementHandler handler = configuration.newStatementHandler(wrapper, ms, parameter, rowBounds, resultHandler, boundSql);
      //创建jdbc的statement对象,把sql的占位符替换成参数
      stmt = prepareStatement(handler, ms.getStatementLog());
      //StatementHandler进行处理
      return handler.<E>query(stmt, resultHandler);
    } finally {
      closeStatement(stmt);
    }
  }
private Statement prepareStatement(StatementHandler handler, Log statementLog) throws SQLException {
    Statement stmt;
    //调用openConnection() 从连接池获得连接 
    Connection connection = getConnection(statementLog);
    stmt = handler.prepare(connection, transaction.getTimeout());
    handler.parameterize(stmt);
    return stmt;
  }
protected void openConnection() throws SQLException {
    if (log.isDebugEnabled()) {
      log.debug("Opening JDBC Connection");
    }
    //从连接池获得连接
    this.connection = this.dataSource.getConnection();
    if (this.level != null) {
      this.connection.setTransactionIsolation(this.level.getLevel());
    }
  }

Executor的作用
1、根据传递的参数,完成SQL语句的动态解析,生成BoundSql对象, 供statementHandler使用 ;
2、为查询创建缓存,以提高性能
3、创建JDBC的Statement连接对象,传递给StatementHandler对象,返回List查询结果。

StatementHandler的作用
1、对于JDBC的PreparedStatement类型的对象,创建的过程中,我们使用的是SQL语句字符串会包含若干个?占位符,我们其后再对占位符进行设值。StatementHandler通过parameterize(statement)方法对Statement进行设值;
2、StatementHandler通过List query(Statement statement, ResultHandler resultHandler)方法来完成执行Statement, 然后将Statement对象返回的resultSet封装成List;

进入org.apache.ibatis.executor.statement.PreparedStatementHandler#parameterize

  @Override
  public void parameterize(Statement statement) throws SQLException {
  	//完成对statement的设值
    parameterHandler.setParameters((PreparedStatement) statement);
  }
@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);
          }
          //每一个Mapping都有一个TypeHandler, 根据TypeHandler来对preparedStatement进行设置参数
          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);
          }
        }
      }
    }
  }

进入PreparedStatementHandler

@Override
  public <E> List<E> query(Statement statement, ResultHandler resultHandler) throws SQLException {
    PreparedStatement ps = (PreparedStatement) statement;
    //执行查询
    ps.execute();
    //处理结果集
    return resultSetHandler.<E> handleResultSets(ps);
  }

进入DefaultResultSetHandler

@Override
  public List<Object> handleResultSets(Statement stmt) throws SQLException {
    ErrorContext.instance().activity("handling results").object(mappedStatement.getId());
	//多ResultSet的结果集合,每个ResultSet 对应一个Object 对象。而实际上,每个object是List<Object>对象。
	//在不考虑存储过程的多ResultSet 的情况,普通的查询,实际就一个ResultSet ,也就是说,multipleResults 最多就一个元素 。	
	//假如查询user表即multipleResults.get(0)=list<user>
    final List<Object> multipleResults = new ArrayList<Object>();

    int resultSetCount = 0;
    //获得首个ResultSet对象,并封装成ResultSetWrapper 对象
    ResultSetWrapper rsw = getFirstResultSet(stmt);
	//用来接收返回list的resulttype
    List<ResultMap> resultMaps = mappedStatement.getResultMaps();
    int resultMapCount = resultMaps.size();
    validateResultMapsCount(rsw, resultMapCount);
    while (rsw != null && resultMapCount > resultSetCount) {
      //获得返回类型
      ResultMap resultMap = resultMaps.get(resultSetCount);
      //处理ResultSet将结果添加到multipleResults中
      handleResultSet(rsw, resultMap, multipleResults, null);
      //获得下一个ResultSet对象,并封装成ResultSetWrapper对象
      rsw = getNextResultSet(stmt);
      //清理
      cleanUpAfterHandlingResultSet();
      resultSetCount++;
    }
	
	//对存储过程的结果处理
    String[] resultSets = mappedStatement.getResultSets();
    if (resultSets != null) {
      while (rsw != null && resultSetCount < resultSets.length) {
        ResultMapping parentMapping = nextResultMaps.get(resultSets[resultSetCount]);
        if (parentMapping != null) {
          String nestedResultMapId = parentMapping.getNestedResultMapId();
          ResultMap resultMap = configuration.getResultMap(nestedResultMapId);
          handleResultSet(rsw, resultMap, null, parentMapping);
        }
        rsw = getNextResultSet(stmt);
        cleanUpAfterHandlingResultSet();
        resultSetCount++;
      }
    }
	//如果multipleResults 单元素,则取首元素返回
    return collapseSingleResultList(multipleResults);
  }

mapper接口被代理

mapper接口没有实现方法却可以使用,因为它使用了动态代理

UserMapper mapper = sqlSession.getMapper(UserMapper.class); 
List<User> list = mapper.getUserByName("tom");

进入DefaultSqlSession

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

进入Configuration

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

进入MapperRegistry

public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
	//从MapperRegistry中的HashMap中拿MapperProxyFactory (解析<mappers>标签的时候放进去的)
    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

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

进入MapperProxy

public class MapperProxy<T> implements InvocationHandler, Serializable {

  private static final long serialVersionUID = -6424540398559729838L;
  private final SqlSession sqlSession;
  private final Class<T> mapperInterface;
  private final Map<Method, MapperMethod> methodCache;
  //构造,传入了SqlSession, 说明每个session中的代理对象的不同的!
  public MapperProxy(SqlSession sqlSession, Class<T> mapperInterface, Map<Method, MapperMethod> methodCache) {
    this.sqlSession = sqlSession;
    this.mapperInterface = mapperInterface;
    this.methodCache = methodCache;
  }

  @Override
  public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
    try {
      //如果是object 定义的方法,直接调用
      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);
    }
    //获得mappermethod对象
    final MapperMethod mapperMethod = cachedMapperMethod(method);
    // MapperMethod最终调用了执行的方法
    return mapperMethod.execute(sqlSession, args);
  }
···

进入MapperMethod

public Object execute(SqlSession sqlSession, Object[] args) {
    Object result;
    //判断mapper中的方法类型,最终调用的还是SqlSession中的方法
    switch (command.getType()) {
      case INSERT: {
      	//转换参数
    	Object param = method.convertArgsToSqlCommandParam(args);
    	//执行插入操作
    	//转换rowcount
        result = rowCountResult(sqlSession.insert(command.getName(), param));
        break;
      }
      case UPDATE: {
        Object param = method.convertArgsToSqlCommandParam(args);
        result = rowCountResult(sqlSession.update(command.getName(), param));
        break;
      }
      case DELETE: {
        Object param = method.convertArgsToSqlCommandParam(args);
        result = rowCountResult(sqlSession.delete(command.getName(), param));
        break;
      }
      case SELECT:
      // 无返回, 并且有ResultHandler 方法参数,则将查询的结果, 提交给ResultHandler进行处理
        if (method.returnsVoid() && method.hasResultHandler()) {
          executeWithResultHandler(sqlSession, args);
          result = null;
          //执行查询,返回列表
        } else if (method.returnsMany()) {
          result = executeForMany(sqlSession, args);
        } else if (method.returnsMap()) {
        //返回map
          result = executeForMap(sqlSession, args);
        } else if (method.returnsCursor()) {
        //返回cursor
          result = executeForCursor(sqlSession, args);
        } else {
        //返回单个对象
          Object param = method.convertArgsToSqlCommandParam(args);
          result = sqlSession.selectOne(command.getName(), param);
        }
        break;
      case FLUSH:
        result = sqlSession.flushStatements();
        break;
      default:
        throw new BindingException("Unknown execution method for: " + command.getName());
    }
    //返回结果为null ,并且返回类型为基本类型,则抛出BindingException 异常
    if (result == null && method.getReturnType().isPrimitive() && !method.returnsVoid()) {
      throw new BindingException("Mapper method '" + command.getName() 
          + " attempted to return null from a method with a primitive return type (" + method.getReturnType() + ").");
    }
    return result;
  }

mybatis在spring的加载

	<bean id="sqlSessionFactory" class="org.mybatis.spring.SqlSessionFactoryBean">
        <!--别名映射扫描-->
        <property name="typeAliasesPackage" value="com.lagou.edu.pojo"/>
        <!--数据源dataSource-->
        <property name="dataSource" ref="dataSource"/>
    </bean>

    <!--Mapper动态代理对象交给Spring管理,我们从Spring容器中直接获得Mapper的代理对象-->
    <!--扫描mapper接口,生成代理对象,生成的代理对象会存储在ioc容器中-->
    <bean class="org.mybatis.spring.mapper.MapperScannerConfigurer">
        <!--mapper接口包路径配置-->
        <property name="basePackage" value="com.lagou.edu.mapper"/>
        <property name="sqlSessionFactoryBeanName" value="sqlSessionFactory"/>
    </bean>

进入SqlSessionFactoryBean发现它实现了InitializingBean接口,在spring生命周期中类被实例化后会调用afterPropertiesSet()方法来初始化这个对象
进入SqlSessionFactoryBean

@Override
  public void afterPropertiesSet() throws Exception {
    notNull(dataSource, "Property 'dataSource' is required");
    notNull(sqlSessionFactoryBuilder, "Property 'sqlSessionFactoryBuilder' is required");
    state((configuration == null && configLocation == null) || !(configuration != null && configLocation != null),
        "Property 'configuration' and 'configLocation' can not specified with together");
    this.sqlSessionFactory = buildSqlSessionFactory();
  }
 protected SqlSessionFactory buildSqlSessionFactory() throws Exception {

    final Configuration targetConfiguration;

    XMLConfigBuilder xmlConfigBuilder = null;
    if (this.configuration != null) {
      targetConfiguration = this.configuration;
      if (targetConfiguration.getVariables() == null) {
        targetConfiguration.setVariables(this.configurationProperties);
      } else if (this.configurationProperties != null) {
        targetConfiguration.getVariables().putAll(this.configurationProperties);
      }
    } else if (this.configLocation != null) {
    //在这里解析xml文件
      xmlConfigBuilder = new XMLConfigBuilder(this.configLocation.getInputStream(), null, this.configurationProperties);
      targetConfiguration = xmlConfigBuilder.getConfiguration();
    } else {
      LOGGER.debug(
          () -> "Property 'configuration' or 'configLocation' not specified, using default MyBatis Configuration");
      targetConfiguration = new Configuration();
      Optional.ofNullable(this.configurationProperties).ifPresent(targetConfiguration::setVariables);
    }
····
	if (this.mapperLocations != null) {
      if (this.mapperLocations.length == 0) {
        LOGGER.warn(() -> "Property 'mapperLocations' was specified but matching resources are not found.");
      } else {
        for (Resource mapperLocation : this.mapperLocations) {
          if (mapperLocation == null) {
            continue;
          }
          try {
            XMLMapperBuilder xmlMapperBuilder = new XMLMapperBuilder(mapperLocation.getInputStream(),
                targetConfiguration, mapperLocation.toString(), targetConfiguration.getSqlFragments());
            //这里解析/mapper节点下的
            xmlMapperBuilder.parse();
          } catch (Exception e) {
            throw new NestedIOException("Failed to parse mapping resource: '" + mapperLocation + "'", e);
          } finally {
            ErrorContext.instance().reset();
          }
          LOGGER.debug(() -> "Parsed mapper file: '" + mapperLocation + "'");
        }
      }
    } else {
      LOGGER.debug(() -> "Property 'mapperLocations' was not specified.");
    }
}

然后就和前面正常解析mybatis流程一样最后addMappedStatement
然后去看MapperScannerConfigurer
MapperScannerConfigurer 实现了BeanDefinitionRegistryPostProcessor接口,BeanDefinitionRegistryPostProcessor继承了BeanFactoryPostProcessor接口,在spring注册beandefinition的时候会调用BeanDefinitionRegistryPostProcessor的postProcessBeanDefinitionRegistry()方法

public void postProcessBeanDefinitionRegistry(BeanDefinitionRegistry registry) {
    if (this.processPropertyPlaceHolders) {
      processPropertyPlaceHolders();
    }

    ClassPathMapperScanner scanner = new ClassPathMapperScanner(registry);
    scanner.setAddToConfig(this.addToConfig);
    scanner.setAnnotationClass(this.annotationClass);
    scanner.setMarkerInterface(this.markerInterface);
    scanner.setSqlSessionFactory(this.sqlSessionFactory);
    scanner.setSqlSessionTemplate(this.sqlSessionTemplate);
    scanner.setSqlSessionFactoryBeanName(this.sqlSessionFactoryBeanName);
    scanner.setSqlSessionTemplateBeanName(this.sqlSessionTemplateBeanName);
    scanner.setResourceLoader(this.applicationContext);
    scanner.setBeanNameGenerator(this.nameGenerator);
    scanner.setMapperFactoryBeanClass(this.mapperFactoryBeanClass);
    if (StringUtils.hasText(lazyInitialization)) {
      scanner.setLazyInitialization(Boolean.valueOf(lazyInitialization));
    }
    scanner.registerFilters();
    //这里最后将dao接口封装成beandefinition,并将definition.setBeanClass(this.mapperFactoryBeanClass);设置成MapperFactoryBean.class;
    scanner.scan(
        StringUtils.tokenizeToStringArray(this.basePackage, ConfigurableApplicationContext.CONFIG_LOCATION_DELIMITERS));
  }

因为beandefinition的class已经设置成了MapperFactoryBean,MapperFactoryBean又实现了initializingbean
在这里插入图片描述

所以它会在实例化后调用afterPropertiesSet方法
在这里插入图片描述
在checkDaoConfig方法中,最后会生成dao的代理对象MapperProxyFactory,并添加到knowmapper
在这里插入图片描述
在这里插入图片描述
最后它会把mapper接口修改beanDefinition后实例化生成的mapperFactoryBean放到spring容器里面
在这里插入图片描述
mapperFactoryBean又实现了FactoryBean接口
在这里插入图片描述
所以在service 注入 dao 的时候会调用
在这里插入图片描述
方法来注入依赖的dao,而这个方法是通过从knownmappers中获得的mapperProxyFactory来实例化对象的
在这里插入图片描述
mapperProxyFactory.newInstance(sqlSession)最终会返回一个mapperProxy的代理对象在这里插入图片描述
所以说service最终注入的mapper是一个mapperProxy的代理对象
在这里插入图片描述

所以调用在mapper方法的时候,实际会进入mapperProxy的invoke方法
在这里插入图片描述
然后在mapperMethod.execute(sqlSession, args)方法里面会执行对应的sql
在这里插入图片描述
在这里插入图片描述

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值