spring mybatis circular reference

摘要: Error creating bean with name 'ＸＸＸ': Requested bean is currently in creation: Is there an unresolvable circular reference?; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException:

如果把MapperScan單獨配置，就不會有警告

DataSource，SqlSessionFactory，MapperScan有依賴關系．

如果把MapperScan單獨配置，就不會有警告，例如：

code：

DataSource:

import com.alibaba.druid.spring.boot.autoconfigure.DruidDataSourceBuilder;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.Primary;

import javax.sql.DataSource;

@Configuration
public class DataSourceConfig {

    @ConfigurationProperties("spring.datasource.druid")
    @Bean
    public DataSource equipDataSource() {
        return DruidDataSourceBuilder.create().build();
    }


}

SqlSessionFactory:

import org.apache.ibatis.session.SqlSessionFactory;
import org.mybatis.spring.SqlSessionFactoryBean;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.core.io.support.PathMatchingResourcePatternResolver;

import javax.sql.DataSource;

@SuppressWarnings("SpringJavaAutowiringInspection")
@Configuration
public class MyBatisConfig {

    @Bean
    public SqlSessionFactory sqlSessionFactory(DataSource dataSource) throws Exception {
        PathMatchingResourcePatternResolver resolver = new PathMatchingResourcePatternResolver();
        SqlSessionFactoryBean factoryBean = new SqlSessionFactoryBean();
        factoryBean.setDataSource(dataSource);
        factoryBean.setTypeAliasesPackage("com.app.domain.entity");// 指定基包
        factoryBean.setMapperLocations(resolver.getResources("classpath:mapper/**/*.xml"));//
        return factoryBean.getObject();
    }

}

MapperScannerConfigurer

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import tk.mybatis.mapper.common.BaseMapper;
import tk.mybatis.spring.mapper.MapperScannerConfigurer;

import java.util.Properties;

@Configuration
public class MapperConfig {

    @Bean
    public MapperScannerConfigurer mapperScannerConfigurer() {
        MapperScannerConfigurer mapperScannerConfigurer = new MapperScannerConfigurer();
        mapperScannerConfigurer.setBasePackage("com.app.domain.mapper");
        Properties properties = new Properties();
        // 這里要特別注意，不要把BaseMapper放到 basePackage 中，也就是不能同其他Mapper一樣被掃描到。
        properties.setProperty("notEmpty", "false");
        properties.setProperty("IDENTITY", "MYSQL");
        mapperScannerConfigurer.setProperties(properties);
        mapperScannerConfigurer.setMarkerInterface(BaseMapper.class); 
        return mapperScannerConfigurer;
    }

}

 

 

 

 

https://my.oschina.net/doctor2014/blog/386431

 

Requested bean is currently in creation: Is there an unresolvable circular reference?

 getBean的時候由於bean之間存在循環依賴出現類似的錯誤，先做一個簡單實驗模擬一下這個異常出現的原因：

bean.xml配置如下：

<?xml version="1.0" encoding="GBK"?>

<beans xmlns="http://www.springframework.org/schema/beans"

       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"

       default-autowire="byName">

<bean id="a" class="BeanA" scope="prototype"/>

<bean id="b" class="BeanB" scope="prototype"/>

</beans>

 

BeanA類如下：

public class BeanA 

{

private BeanB b;

public BeanB getB() {

return b;

}

public void setB(BeanB b) {

this.b = b;

}

}

 

BeanB類如下：

public class BeanB 

{

private BeanA a;

public BeanA getA() {

return a;

}

public void setA(BeanA a) {

this.a = a;

}

}

程序執行的堆棧信息：

 

bean在初始化的同時會初始化相應的屬性（byName），a在初始化的時候會創建a.b，a.b在初始化的時候會創建a.b.a，形成了一個環，所以在AbstractBeanFactory.doGetBean（這里會出現遞歸調用） 時候 ，走到：

if (isPrototypeCurrentlyInCreation(beanName)) {

throw new BeanCurrentlyInCreationException(beanName);

}

會拋出一個異常：Requested bean is currently in creation: Is there an unresolvable circular reference，然后scope是singlton或者其他的時候bean的創建過程不一樣，不會有一個這樣子的判斷，因而不會拋出這樣子的錯誤。

因為scope=prototype，所以每次請求對應不同的bean，所以在創建的時候有一個依賴的先后順序，而如果bean配置成singleton，則屬性間初始化的順序可以無所謂了，所有的bean都只有一份，所以在bean是singleton時候不會報unresolvable circular reference的錯誤。