Spring源码解析 – @Configuration配置类及注解Bean的解析

在分析Spring 容器创建过程时,我们知道容器默认会加载一些后置处理器PostPRocessor,以AnnotationConfigApplicationContext为例,在构造函数中初始化reader时,加载默认后置处理器。其中 ConfigurationClassPostProcessor这个后置处理器专门处理带有@Configuration注解的类,ConfigurationClassPostProcessor后置处理实现了BeanDefinitionRegistryPostProcessor接口和PriorityOrdered接口,所以会在容器初始化refres()方法中执行后置处理器时优先执行,主要负责解析所有@Configuration标签类,并将Bean定义注册到容器中。

BeanDefinitionRegistryPostProcessor解析配置类过程:

复制代码
1 public void postProcessBeanDefinitionRegistry(BeanDefinitionRegistry registry) {
2 //生成唯一标识,用于重复处理验证
3 int registryId = System.identityHashCode(registry);
4 if (this.registriesPostProcessed.contains(registryId)) {
5 throw new IllegalStateException(
6 "postProcessBeanDefinitionRegistry already called on this post-processor against " + registry);
7 }
8 if (this.factoriesPostProcessed.contains(registryId)) {
9 throw new IllegalStateException(
10 "postProcessBeanFactory already called on this post-processor against " + registry);
11 }
12 this.registriesPostProcessed.add(registryId);
13 //解析Java类配置bean
14 processConfigBeanDefinitions(registry);
15 }
复制代码
processConfigBeanDefinitions(registry)处理逻辑:
复制代码
1 public void processConfigBeanDefinitions(BeanDefinitionRegistry registry) {
2 List configCandidates = new ArrayList<>();
3   //所有已经注册的bean
4 String[] candidateNames = registry.getBeanDefinitionNames();
5 //遍历bean定义信息
6 for (String beanName : candidateNames) {
7 BeanDefinition beanDef = registry.getBeanDefinition(beanName);
8 if (ConfigurationClassUtils.isFullConfigurationClass(beanDef) ||
9 ConfigurationClassUtils.isLiteConfigurationClass(beanDef)) {
10 if (logger.isDebugEnabled()) {
11 logger.debug("Bean definition has already been processed as a configuration class: " + beanDef);
12 }
13 }
14   //如果当前的bean是Javabean配置类(含有@Configuration注解的类),则加入到集合configCandidates中,
15 else if (ConfigurationClassUtils.checkConfigurationClassCandidate(beanDef, this.metadataReaderFactory)) {
16 configCandidates.add(new BeanDefinitionHolder(beanDef, beanName));
17 }
18 }
19
20 // Return immediately if no @Configuration classes were found
21   // 没有@Configuration注解的类,直接退出
22 if (configCandidates.isEmpty()) {
23 return;
24 }
25
26 // 多个Java配置类,按@Ordered注解排序
27 configCandidates.sort((bd1, bd2) -> {
28 int i1 = ConfigurationClassUtils.getOrder(bd1.getBeanDefinition());
29 int i2 = ConfigurationClassUtils.getOrder(bd2.getBeanDefinition());
30 return Integer.compare(i1, i2);
31 });
32
33 // Detect any custom bean name generation strategy supplied through the enclosing application context
34 SingletonBeanRegistry sbr = null;
35 if (registry instanceof SingletonBeanRegistry) {
36 sbr = (SingletonBeanRegistry) registry;
37 if (!this.localBeanNameGeneratorSet) {
38 BeanNameGenerator generator = (BeanNameGenerator) sbr.getSingleton(CONFIGURATION_BEAN_NAME_GENERATOR);
39 if (generator != null) {
40 this.componentScanBeanNameGenerator = generator;
41 this.importBeanNameGenerator = generator;
42 }
43 }
44 }
45
46 if (this.environment == null) {
47 this.environment = new StandardEnvironment();
48 }
49
50 // Parse each @Configuration class
51   //初始化一个ConfigurationClassParser解析器,可以解析@Congiguration配置类
52 ConfigurationClassParser parser = new ConfigurationClassParser(
53 this.metadataReaderFactory, this.problemReporter, this.environment,
54 this.resourceLoader, this.componentScanBeanNameGenerator, registry);
55
56 Set candidates = new LinkedHashSet<>(configCandidates);
57 Set alreadyParsed = new HashSet<>(configCandidates.size());
58 do {
59     //1.解析Java配置类
60 parser.parse(candidates);
61     //主要校验配置类不能使用final修饰符(CGLIB代理是生成一个子类,因此原先的类不能使用final修饰)
62 parser.validate();
63
64 //排除已处理过的配置类
65 Set configClasses = new LinkedHashSet<>(parser.getConfigu

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值