循環依賴其實就是循環引用,也就是兩個或則兩個以上的 Bean 互相持有對方,最終造成閉環。好比A依賴於B,B依賴於C,C又依賴於A。以下圖:java
若是在平常開發中咱們用new 對象的方式發生這種循環依賴的話程序會在運行時一直循環調用,直至內存溢出報錯。下面說一下Spring是若是解決循環依賴的。spring
注意,這裏不是函數的循環調用,是對象的相互依賴關係。循環調用其實就是一個死循環,除非有終結條件。緩存
根據 spring 中 Bean 的注入方式:構造器注入方式,屬性注入方式(單例和多例),咱們分別來說解循環依賴的處理方式。app
Spring容器會將每個正在建立的 Bean 標識符放在一個「當前建立Bean池」中,Bean標識符在建立過程當中將一直保持在這個池中,所以若是在建立Bean過程當中發現本身已經在「當前建立Bean池」裏時將拋出BeanCurrentlyInCreationException
異常表示循環依賴;而對於建立完畢的Bean將從「當前建立Bean池」中清除掉。函數
首先咱們先初始化三個Bean。學習
StudentA 測試
public class StudentA { private StudentB studentB ; public void setStudentB(StudentB studentB) { this.studentB = studentB; } public StudentA() { } public StudentA(StudentB studentB) { this.studentB = studentB; } }
StudentB ui
public class StudentB { private StudentC studentC ; public void setStudentC(StudentC studentC) { this.studentC = studentC; } public StudentB() { } public StudentB(StudentC studentC) { this.studentC = studentC; } }
StudentC this
public class StudentC { private StudentA studentA ; public void setStudentA(StudentA studentA) { this.studentA = studentA; } public StudentC() { } public StudentC(StudentA studentA) { this.studentA = studentA; } }
OK,上面是很基本的3個類,StudentA 有參構造是 StudentB 。StudentB 的有參構造是 StudentC,StudentC 的有參構造是 StudentA ,這樣就產生了一個循環依賴的狀況,咱們都把這三個 Bean 交給 Spring 管理,並用有參構造實例化。.net
<bean id="a" class="com.zfx.student.StudentA"> <constructor-arg index="0" ref="b"></constructor-arg> </bean> <bean id="b" class="com.zfx.student.StudentB"> <constructor-arg index="0" ref="c"></constructor-arg> </bean> <bean id="c" class="com.zfx.student.StudentC"> <constructor-arg index="0" ref="a"></constructor-arg> </bean>
下面是測試類:
public class Test { public static void main(String[] args) { ApplicationContext context = new ClassPathXmlApplicationContext("com/zfx/student/applicationContext.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?
若是你們理解開頭那句話的話,這個報錯應該不驚訝,Spring容器先建立單例StudentA,StudentA依賴StudentB,而後將A放在「當前建立Bean池」中,此時建立 StudentB,StudentB 依賴 StudentC ,而後將B放在「當前建立Bean池」中,此時建立StudentC,StudentC又依賴StudentA, 可是,此時Student已經在池中,因此會報錯,由於在池中的Bean都是未初始化完的,因此會依賴錯誤 (初始化完的Bean會從池中移除)。
若是要說setter方式注入的話,咱們最好先看一張Spring中Bean實例化的圖
如圖中前兩步驟得知:Spring是先將Bean對象實例化以後再設置對象屬性的
修改配置文件爲set方式注入
<!--scope="singleton"(默認就是單例方式) --> <bean id="a" class="com.zfx.student.StudentA" scope="singleton"> <property name="studentB" ref="b"></property> </bean> <bean id="b" class="com.zfx.student.StudentB" scope="singleton"> <property name="studentC" ref="c"></property> </bean> <bean id="c" class="com.zfx.student.StudentC" scope="singleton"> <property name="studentA" ref="a"></property> </bean>
下面是測試類:
public class Test { public static void main(String[] args) { ApplicationContext context = new ClassPathXmlApplicationContext("com/zfx/student/applicationContext.xml"); System.out.println(context.getBean("a", StudentA.class)); } }
打印結果爲:
com.zfx.student.StudentA@1fbfd6
爲何用set方式就不報錯了呢 ?
咱們結合上面那張圖看,Spring先是用構造實例化Bean對象 ,此時Spring會將這個實例化結束的對象放到一個Map中,而且Spring提供了獲取這個未設置屬性的實例化對象引用的方法。 結合咱們的實例來看,當Spring實例化了StudentA、StudentB、StudentC後,緊接着會去設置對象的屬性,此時StudentA依賴StudentB,就會去Map中取出存在裏面的單例StudentB對象,以此類推,不會出來循環的問題嘍。
下面是Spring源碼中的實現方法。如下的源碼在Spring的Bean包中的DefaultSingletonBeanRegistry.java
類中:
/** 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); } } }
修改配置文件爲:
<bean id="a" class="com.zfx.student.StudentA" scope="prototype"> <property name="studentB" ref="b"></property> </bean> <bean id="b" class="com.zfx.student.StudentB" scope="prototype"> <property name="studentC" ref="c"></property> </bean> <bean id="c" class="com.zfx.student.StudentC" scope="prototype"> <property name="studentA" ref="a"></property> </bean>
scope="prototype" 意思是 每次請求都會建立一個實例對象。二者的區別是:有狀態的bean都使用 prototype 做用域,無狀態的通常都使用singleton單例做用域。
測試用例:
public class Test { public static void main(String[] args) { ApplicationContext context = new ClassPathXmlApplicationContext("com/zfx/student/applicationContext.xml"); //此時必需要獲取Spring管理的實例,由於如今scope="prototype" 只有請求獲取的時候纔會實例化對象 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?
爲何原型模式就報錯了呢 ?
對於「prototype」做用域Bean,Spring容器沒法完成依賴注入,由於「prototype」做用域的Bean,Spring容器不進行緩存,所以沒法提早暴露一個建立中的Bean。
來源於:學習園