Configuration源碼,你了解多少?
Configuration
最近看源碼時(shí),經(jīng)??戳讼翤Configuration(proxyBeanMethods = false)這樣的配置,但從命名上看應(yīng)該是與代理有關(guān)的,于是抽個(gè)時(shí)間了解了下
proxyBeanMethods
首先這個(gè)是@Configuration注解中的一個(gè)參數(shù),我們都知道,@Configuration是Spring中的配置類,一般用來(lái)申明Bean,在默認(rèn)情況下proxyBeanMethods為true
含義
從源碼中可以看到對(duì)該參數(shù)的描述如下:
Specify whether @Bean methods should get proxied in order to enforce bean lifecycle behavior, e.g. to return shared singleton bean instances even in case of direct @Bean method calls in user code. This feature requires method interception, implemented through a runtime-generated CGLIB subclass which comes with limitations such as the configuration class and its methods not being allowed to declare final.
The default is true, allowing for 'inter-bean references' via direct method calls within the configuration class as well as for external calls to this configuration's @Bean methods, e.g. from another configuration class. If this is not needed since each of this particular configuration's @Bean methods is self-contained and designed as a plain factory method for container use, switch this flag to false in order to avoid CGLIB subclass processing.
Turning off bean method interception effectively processes @Bean methods individually like when declared on non-@Configuration classes, a.k.a. "@Bean Lite Mode" (see @Bean's javadoc). It is therefore behaviorally equivalent to removing the @Configuration stereotype.
- 該屬性的作用是指定標(biāo)注了@Bean的方法在執(zhí)行生命周期的時(shí)候是否應(yīng)該被代理。比如在代碼中直接調(diào)用@Bean標(biāo)注的方法時(shí)要返回共享的單例Bean實(shí)例(關(guān)閉代理之后不會(huì)返回共享的Bean實(shí)例)。
- 該特性是通過(guò)運(yùn)行時(shí)CGLIB子類 實(shí)現(xiàn)的方法攔截。該子類有一些限制,比如配置類和它的方法不允許聲明為final類型。
- 默認(rèn)為true,即允許 “inter-bean references” 通過(guò)配置類內(nèi)部的直接方法調(diào)用,也可以通過(guò)外部調(diào)用該配置類的@Bean標(biāo)注的方法。如果該配置類是一個(gè)特殊的配置類:每一個(gè)@Bean標(biāo)注的方法 都是自包含的,并設(shè)計(jì)為供容器使用的普通工廠方法,可以設(shè)置該屬性為false,以避免CGLIB子類處理。
- 關(guān)閉Bean方法攔截可以高效的單獨(dú)處理@Bean方法,就像聲明在一個(gè)non-@Configuration類上一樣,@Bean Lite Mode。這種行為類似于刪除@Configuration原型。
當(dāng)直接在Configuration中直接通過(guò)方法,實(shí)現(xiàn)實(shí)例件的屬性依賴時(shí),IDEA會(huì)有這樣一段提示:
Method annotated with @Bean is called directly in a @Configuration where proxyBeanMethods set to false. Set proxyBeanMethods to true or use dependency injection.
示例
先通過(guò)下面的示例看下現(xiàn)象:
兩個(gè)配置類,寫法差不多,區(qū)別在與proxyBeanMethods的配置以及AnimalCage屬性的注入方法。
@Configuration(proxyBeanMethods = false)
public class GenericConfiguration {
@Bean
public DogCage dogCage(){
return new DogCage();
}
@Bean
public AnimalCage animalEden(){
AnimalCage animalCage = new AnimalCage();
animalCage.addCage(dogCage());
return animalCage;
}
}
@Configuration(proxyBeanMethods = true)
public class ProxyConfiguration {
@Bean
public DogCage dogCage(){
return new DogCage();
}
@Bean
public AnimalCage animalEden(@Autowired List<Cage> cages){
return new AnimalCage(cages);
}
}
先看下GenericConfiguration配置的情況:
public class Tests {
@Autowired
private BeanFactory beanFactory;
@Autowired
private GenericConfiguration genericConfiguration;
@Autowired
private AnimalCage animalCage;
@Autowired
private DogCage dogCage;
@Test
public void runConfig() {
log.info("configuration: {}", genericConfiguration); // 原始對(duì)象類型
log.info("Configuration中的Bean: {}", genericConfiguration.dogCage() == genericConfiguration.dogCage()); // 兩次結(jié)果不一樣
log.info("容器中的Bnea: {}", beanFactory.getBean(DogCage.class) == beanFactory.getBean(DogCage.class));// 從Spring容器中取值都是一樣的
animalCage.cages.forEach(cage -> {
if (cage instanceof DogCage) {
log.info("dogCage : {} ", cage == dogCage); // 和上面的對(duì)象不一致,非單例
}
});
}
}
再看下ProxyConfiguration配置的情況:
public class Tests {
@Test
public void runConfig() {
log.info("configuration: {}", proxyConfiguration); // 1、CGLIB代理的對(duì)象
log.info("Configuration中的Bean: {}", proxyConfiguration.dogCage() == proxyConfiguration.dogCage()); // 2、兩次結(jié)果相同
log.info("容器中的Bnea: {}", beanFactory.getBean(DogCage.class) == beanFactory.getBean(DogCage.class));// 3、從Spring容器中取值都是一樣的
animalCage.cages.forEach(cage -> {
if (cage instanceof DogCage) {
log.info("dogCage : {} ", cage == dogCage); // 和上面的對(duì)象不一致,非單例
}
});
}
}
會(huì)得到這樣的現(xiàn)象:
- proxyBeanMethods = true時(shí),從Spring容器中取出的Configuration是一個(gè)Cglib代理配置,否則是一個(gè)原始類型配置
- proxyBeanMethods = true時(shí),多次調(diào)用Bean方法,每次都是一個(gè)新對(duì)象,否則都是同一個(gè)對(duì)象
- 從Spring容器中取出Bean,不管多少次,都是同一個(gè)對(duì)象,也就是單例的
Lite Full Mode
看到上面的現(xiàn)象后,我們有必要了解下Spring配置中的Lite和Full兩種模式
lite模式包含:
- 被@Component修飾的類
- 通過(guò)@ComponentScan掃描的類
- 通過(guò)@Import導(dǎo)入的配置類
- 通過(guò)@ImportResource導(dǎo)入的Spring配置文件
- 沒(méi)有任何Spring相關(guān)注解,類里面有@Bean修飾的方法
- 被@Configuration修飾,但proxyBeanMethods = false
full模式包含:
- 被@Configuration修飾,且屬性proxyBeanMethods = true(默認(rèn))
full模式使用特性:
- full模式下的配置類會(huì)被Cglib代理生成代理類取代原始類型保存到在容器中
- full模式下的@Bean方法不能是private和final,因?yàn)榉椒〞?huì)被重寫
- 單例scope下不同@Bean方法可以互相引用,實(shí)現(xiàn)單實(shí)例的語(yǔ)義
lite模式使用特性:
- lite模式下的配置類不生成代理,原始類型進(jìn)入容器
- lite模式下的@Bean方法可以是private和final
- 單例scope下不同@Bean方法引用時(shí)無(wú)法做到單例,通過(guò)@Bean方法生成的對(duì)象都是新的實(shí)例
結(jié)束語(yǔ)
@Configuration(proxyBeanMethods = false)的配置其實(shí)是Lite模式,這種模式下,配置類不會(huì)生成代理類,速度會(huì)更快,但是要注意,在配置類中的@Bean方法,不能用來(lái)實(shí)現(xiàn)單例級(jí)別的依賴。