spring registerBeanPostProcessors 分析

最新推荐文章于 2023-10-03 23:18:48 发布

weixin_46564779

最新推荐文章于 2023-10-03 23:18:48 发布

阅读量58

点赞数

文章标签： spring java 后端

本文链接：https://blog.csdn.net/weixin_46564779/article/details/129203749

版权

过程很简单，就是创建并往容器放入 BeanProcessor ，但是并没有执行

就简单讲讲 BeanPostProcessorChecker 和 ApplicationListenerDetector 作用

 public static void registerBeanPostProcessors(ConfigurableListableBeanFactory beanFactory, AbstractApplicationContext applicationContext) {


        //获取BeanPostProcessor 的 bean name
        String[] postProcessorNames = beanFactory.getBeanNamesForType(BeanPostProcessor.class, true, false);

        // Register BeanPostProcessorChecker that logs an info message when
        // a bean is created during BeanPostProcessor instantiation, i.e. when
        // a bean is not eligible for getting processed by all BeanPostProcessors.
        //获取一共有多少个 beanProcessor
        // postProcessorNames 里存放的是我们xml 里定义 postProcessorNames
        // beanFactory.getBeanPostProcessorCount()  获取的是我们方法里添加的  postProcessorNames
        // 至于为什么 +1 ，那是因为后面那里添加了一个 BeanPostProcessorChecker
        int beanProcessorTargetCount = beanFactory.getBeanPostProcessorCount() + 1 + postProcessorNames.length;
        beanFactory.addBeanPostProcessor(new BeanPostProcessorChecker(beanFactory, beanProcessorTargetCount));

        // Separate between BeanPostProcessors that implement PriorityOrdered,
        // Ordered, and the rest.
        //存储实现了 PriorityOrdered 的 BeanPostProcessor 容器
        List<BeanPostProcessor> priorityOrderedPostProcessors = new ArrayList<>();
        //存储实现了 MergedBeanDefinitionPostProcessor 的 BeanPostProcessor 的 容器
        List<BeanPostProcessor> internalPostProcessors = new ArrayList<>();
        //存储实现了 Ordered 的 BeanPostProcessor 的 容器
        List<String> orderedPostProcessorNames = new ArrayList<>();
        //存储其他的 BeanPostProcessor 的容器
        List<String> nonOrderedPostProcessorNames = new ArrayList<>();
        for (String ppName : postProcessorNames) {
            //获取实现了 PriorityOrdered 的 BeanProcessor 添加进容器
            if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
                BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
                priorityOrderedPostProcessors.add(pp);
                if (pp instanceof MergedBeanDefinitionPostProcessor) {
                    internalPostProcessors.add(pp);
                }
            }
            else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
                //添加 Ordered 的 BeanProcessor 添加进容器
                orderedPostProcessorNames.add(ppName);
            }
            else {
                //添加 其他的 BeanProcessor 添加进容器
                nonOrderedPostProcessorNames.add(ppName);
            }
        }
        //对实现了  PriorityOrdered 的BeanPostProcessor 进行排序
        // First, register the BeanPostProcessors that implement PriorityOrdered.
        sortPostProcessors(priorityOrderedPostProcessors, beanFactory);
        //对实现了  PriorityOrdered 的 BeanPostProcessor 进行注册
        registerBeanPostProcessors(beanFactory, priorityOrderedPostProcessors);
        //后续的流程也是一样的，就不做分析了
        // Next, register the BeanPostProcessors that implement Ordered.
        List<BeanPostProcessor> orderedPostProcessors = new ArrayList<>();
        for (String ppName : orderedPostProcessorNames) {
            BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
            orderedPostProcessors.add(pp);
            if (pp instanceof MergedBeanDefinitionPostProcessor) {
                internalPostProcessors.add(pp);
            }
        }
        sortPostProcessors(orderedPostProcessors, beanFactory);
        registerBeanPostProcessors(beanFactory, orderedPostProcessors);

        // Now, register all regular BeanPostProcessors.
        List<BeanPostProcessor> nonOrderedPostProcessors = new ArrayList<>();
        for (String ppName : nonOrderedPostProcessorNames) {
            BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
            nonOrderedPostProcessors.add(pp);
            if (pp instanceof MergedBeanDefinitionPostProcessor) {
                internalPostProcessors.add(pp);
            }
        }
        registerBeanPostProcessors(beanFactory, nonOrderedPostProcessors);

        // Finally, re-register all internal BeanPostProcessors.
        sortPostProcessors(internalPostProcessors, beanFactory);
        registerBeanPostProcessors(beanFactory, internalPostProcessors);

        // Re-register post-processor for detecting inner beans as ApplicationListeners,
        // moving it to the end of the processor chain (for picking up proxies etc).
        beanFactory.addBeanPostProcessor(new ApplicationListenerDetector(applicationContext));
    }

点进去查看

翻译一下

在创建bean时记录信息消息的 BeanPostProcessor

即当bean不符合由该 BeanPostProcessor BeanPostProcessors处理。

其实就是在实例化一些不恰当的 bean 时打印日志

	@Override
		public Object postProcessAfterInitialization(Object bean, String beanName) {
			if (!(bean instanceof BeanPostProcessor) && !isInfrastructureBean(beanName) &&
					this.beanFactory.getBeanPostProcessorCount() < this.beanPostProcessorTargetCount) {
				if (logger.isInfoEnabled()) {
					logger.info("Bean '" + beanName + "' of type [" + bean.getClass().getName() +
							"] is not eligible for getting processed by all BeanPostProcessors " +
							"(for example: not eligible for auto-proxying)");
				}
			}
			return bean;
		}

判断一个bean是否恰当主要由该 isInfrastructureBean 方法判断

至于里面的 role 是如何设置的，我目前也没懂，所以无法模拟这个问题，等到后面解决了再补

private boolean isInfrastructureBean(@Nullable String beanName) {
   if (beanName != null && this.beanFactory.containsBeanDefinition(beanName)) {
      BeanDefinition bd = this.beanFactory.getBeanDefinition(beanName);
      return (bd.getRole() == RootBeanDefinition.ROLE_INFRASTRUCTURE);
   }
   return false;
}