本篇文章解决以下问题:
- [1] . Spring循环依赖指的是什么?
- [2] . Spring能解决哪种情况的循环依赖?不能解决哪种情况?
- [3] . Spring能解决的循环依赖原理(三级缓存)
一、Spring 循环依赖可能出现的三种方式
第一种:构造器参数循环依赖
第二种:setter方式单例,默认方式
第三种:setter方式原型,prototype
第一种:构造器参数循环依赖
首先我们先初始化三个Bean。
public class StudentA {
private StudentB studentB;
public void setStudentB(StudentB studentB) {
this.studentB = studentB;
}
public StudentA() {
}
public StudentA(StudentB studentB) {
this.studentB = studentB;
}
}
public class StudentB {
private StudentC studentC ;
public void setStudentC(StudentC studentC) {
this.studentC = studentC;
}
public StudentB() {
}
public StudentB(StudentC studentC) {
this.studentC = studentC;
}
}
public class StudentC {
private StudentA studentA;
public void setStudentA(StudentA studentA) {
this.studentA = studentA;
}
public StudentC() {
}
public StudentC(StudentA studentA) {
this.studentA = studentA;
}
}
application1.xml
<bean id="a" class="cn.mayday.springrecycledp.demo1.StudentA">
<constructor-arg index="0" ref="b"></constructor-arg>
</bean>
<bean id="b" class="cn.mayday.springrecycledp.demo1.StudentB">
<constructor-arg index="0" ref="c"></constructor-arg>
</bean>
<bean id="c" class="cn.mayday.springrecycledp.demo1.StudentC">
<constructor-arg index="0" ref="a"></constructor-arg>
</bean>
测试类
@Test
public void test1() {
ApplicationContext context = new ClassPathXmlApplicationContext("classpath:applicationContext1.xml");
}
测试结果
Caused by: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'a': Requested bean is currently in creation: Is there an unresolvable circular reference?
- 结果分析
Spring容器会将每一个正在创建的Bean
标识符放在一个“当前创建Bean池”中,Bean标识符在创建过程中将一直保持在这个池中。因此如果在创建Bean过程中发现自己已经在“当前创建Bean池”里时将抛出BeanCurrentlyInCreationException异常表示循环依赖;而对于创建完毕的Bean将从“当前创建Bean池”中清除掉。
- 根据上述源码实现分析:Spring容器先创建单例StudentA,StudentA依赖StudentB,然后将A放在“当前创建Bean池”中,此时创建StudentB, StudentB依赖StudentC ,然后将B放在“当前创建Bean池”中,此时创建StudentC,StudentC又依赖StudentA, 但是,此时StudentA已经在池中,所以会报错,因为在池中的Bean都是未初始化完的,所以会依赖错误 ,(初始化完的Bean会从池中移除)
第二种:setter方式单例,默认方式
application2.xml
<!--scope="singleton"(默认就是单例方式) -->
<bean id="a" class="cn.mayday.springrecycledp.demo1.StudentA" scope="singleton">
<property name="studentB" ref="b"></property>
</bean>
<bean id="b" class="cn.mayday.springrecycledp.demo1.StudentB" scope="singleton">
<property name="studentC" ref="c"></property>
</bean>
<bean id="c" class="cn.mayday.springrecycledp.demo1.StudentC" scope="singleton">
<property name="studentA" ref="a"></property>
</bean>
- 测试类
@Test
public void test2() {
ApplicationContext context = new ClassPathXmlApplicationContext("classpath:applicationContext2.xml");
System.out.println(context.getBean("a", StudentA.class));
}
- 测试结果
没有报错
- 结果分析
如果要说setter方式注入的话,我们最好先看一张Spring中Bean实例化的图
如图中前两步骤得知:Spring是先将Bean对象实例化之后再设置对象属性的
- 为什么用set方式就不报错了呢 ?
结合上面那张图看,Spring先是用构造实例化Bean对象 ,此时Spring会将这个实例化结束的对象放到一个Map中,并且Spring提供了获取这个未设置属性的实例化对象引用的方法。
结合我们的实例来看,,当Spring实例化了StudentA、StudentB、StudentC后,紧接着会去设置对象的属性,此时StudentA依赖StudentB,就会去Map中取出存在里面的单例StudentB对象,以此类推,不会出来循环的问题喽。
第三种:setter方式原型,prototype
application3.xml
<!--scope="prototype" -->
<bean id="a" class="cn.mayday.springrecycledp.demo1.StudentA" scope="prototype">
<property name="studentB" ref="b"></property>
</bean>
<bean id="b" class="cn.mayday.springrecycledp.demo1.StudentB" scope="prototype">
<property name="studentC" ref="c"></property>
</bean>
<bean id="c" class="cn.mayday.springrecycledp.demo1.StudentC" scope="prototype">
<property name="studentA" ref="a"></property>
</bean>
测试类
@Test
public void test3() {
ApplicationContext context = new ClassPathXmlApplicationContext("classpath:applicationContext3.xml");
System.out.println(context.getBean("a", StudentA.class));
}
测试结果
Caused by: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'a': Requested bean is currently in creation: Is there an unresolvable circular reference?
- 为什么原型模式就报错了呢 ?
scope="prototype" 意思是 每次请求都会创建一个实例对象。
两者的区别是:有状态的bean都使用Prototype作用域,无状态的一般都使用singleton单例作用域。
对于“prototype”作用域Bean,Spring容器无法完成依赖注入,因为“prototype”作用域的Bean,Spring容器不进行缓存,因此无法提前暴露一个创建中的Bean。
-
总结
-
1、 Spring bean初始化的循环依赖只能解决单例模式的set方式(依靠==第三级缓存==提前暴露==无参构造函数==new出的对象)
-
2、 scope="prototype"时,三级缓存不保存非单例模式的bean对象,所以无法解决。
二、 Spring解决单例模式循环依赖原理(三级缓存)
Spring三级缓存请参考文章
Spring源码初探-IOC(4)-Bean的初始化-循环依赖的解决(讲的很明白)
/** Cache of singleton objects: bean name --> bean instance(缓存单例实例化对象的Map集合) */
private final Map<String, Object> singletonObjects = new ConcurrentHashMap<String, Object>(64);
/** Cache of singleton factories: bean name --> ObjectFactory(单例的工厂Bean缓存集合) */
private final Map<String, ObjectFactory> singletonFactories = new HashMap<String, ObjectFactory>(16);
/** Cache of early singleton objects: bean name --> bean instance(早期的单身对象缓存集合) */
private final Map<String, Object> earlySingletonObjects = new HashMap<String, Object>(16);
/** Set of registered singletons, containing the bean names in registration order(单例的实例化对象名称集合) */
private final Set<String> registeredSingletons = new LinkedHashSet<String>(64);
/**
* 添加单例实例
* 解决循环引用的问题
* Add the given singleton factory for building the specified singleton
* if necessary.
* <p>To be called for eager registration of singletons, e.g. to be able to
* resolve circular references.
* @param beanName the name of the bean
* @param singletonFactory the factory for the singleton object
*/
protected void addSingletonFactory(String beanName, ObjectFactory singletonFactory) {
Assert.notNull(singletonFactory, "Singleton factory must not be null");
synchronized (this.singletonObjects) {
if (!this.singletonObjects.containsKey(beanName)) {
this.singletonFactories.put(beanName, singletonFactory);
this.earlySingletonObjects.remove(beanName);
this.registeredSingletons.add(beanName);
}
}
}
参考文章:
1 面试必问:Spring 循环依赖的三种方式
2 Spring源码初探-IOC(4)-Bean的初始化-循环依赖的解决(讲的很明白)
欢迎关注微信公众号:shoshana