淺談Spring解決循環依賴的三種方式


引言:循環依賴就是N個類中循環嵌套引用,如果在日常開發中我們用new 對象的方式發生這種循環依賴的話程序會在運行時一直循環調用,直至內存溢出報錯。下面說一下Spring是如果解決循環依賴的。

第一種:構造器參數循環依賴

表示通過構造器注入構成的循環依賴,此依賴是無法解決的,只能拋出BeanCurrentlyIn CreationException異常表示循環依賴。

如在創建TestA類時,構造器需要TestB類,那將去創建TestB,在創建TestB類時又發現需要TestC類,則又去創建TestC,最終在創建TestC時發現又需要TestA,從而形成一個環,沒辦法創建。

Spring容器會將每一個正在創建的Bean 標識符放在一個“當前創建Bean池”中,Bean標識符在創建過程中將一直保持
在這個池中,因此如果在創建Bean過程中發現自己已經在“當前創建Bean池”里時將拋出
BeanCurrentlyInCreationException異常表示循環依賴;而對於創建完畢的Bean將從“當前創建Bean池”中清除掉。

首先我們先初始化三個Bean。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
public class StudentA {
  
  private StudentB studentB ;
  
  public void setStudentB(StudentB studentB) {
  this .studentB = studentB;
  }
  
  public StudentA() {
  }
  
  public StudentA(StudentB studentB) {
  this .studentB = studentB;
  }
}
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
public class StudentB {
  
  private StudentC studentC ;
  
  public void setStudentC(StudentC studentC) {
  this .studentC = studentC;
  }
  
  public StudentB() {
  }
  
  public StudentB(StudentC studentC) {
  this .studentC = studentC;
  }
}
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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管理,並用有參構造實例化

?
1
2
3
4
5
6
7
8
9
< 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 >

下面是測試類:

?
1
2
3
4
5
6
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方式單例,默認方式

如果要說setter方式注入的話,我們最好先看一張Spring中Bean實例化的圖

如圖中前兩步驟得知:Spring是先將Bean對象實例化之后再設置對象屬性的

修改配置文件為set方式注入

?
1
2
3
4
5
6
7
8
9
10
<!--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 >

下面是測試類:

?
1
2
3
4
5
6
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類中

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
/** 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);
   }
  }
  }

第三種:setter方式原型,prototype

對於"prototype"作用域bean,Spring容器無法完成依賴注入,因為Spring容器不進行緩存"prototype"作用域的bean,因此無法提前暴露一個創建中的bean。

修改配置文件為:

?
1
2
3
4
5
6
7
8
9
< bean id = "a" class = "com.zfx.student.StudentA" <span style = "color:#FF0000;" >scope="prototype"</ span >>
  < property name = "studentB" ref = "b" ></ property >
  </ bean >
  < bean id = "b" class = "com.zfx.student.StudentB" <span style = "color:#FF0000;" >scope="prototype"</ span >>
  < property name = "studentC" ref = "c" ></ property >
  </ bean >
  < bean id = "c" class = "com.zfx.student.StudentC" <span style = "color:#FF0000;" >scope="prototype"</ span >>
  < property name = "studentA" ref = "a" ></ property >
  </ bean >

scope="prototype" 意思是 每次請求都會創建一個實例對象。兩者的區別是:有狀態的bean都使用Prototype作用域,無狀態的一般都使用singleton單例作用域。

測試用例:

?
1
2
3
4
5
6
7
public class Test {
  public static void main(String[] args) {
  ApplicationContext context = new ClassPathXmlApplicationContext( "com/zfx/student/applicationContext.xml" );
  <strong> //此時必須要獲取Spring管理的實例,因為現在scope="prototype" 只有請求獲取的時候才會實例化對象</strong>
  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。

以上就是本文的全部內容,希望對大家的學習有所幫助,也希望大家多多支持腳本之家。

 

原文鏈接:http://blog.csdn.net/u010644448/article/details/59108799


免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM