Spring容器创建流程（4）调用beanFactory后置处理器

postProcessBeanFactory() 方法留给子类去实现。

invokeBeanFactoryPostProcessors() 调用bean工厂的后置处理器（以前的执行流程可在系列文章中查看）

容器refresh总览：

     synchronized (this.startupShutdownMonitor) {// 设置环境，校验参数。prepareRefresh();// 创建BeanFactory（DefaultListableBeanFactor），加载bean定义信息。ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();// 对BeanFactory设置  prepareBeanFactory(beanFactory);try {// 留给子类去实现，完成对beanFactory的自定义处理postProcessBeanFactory(beanFactory);// 调用beanFactory的后置处理器invokeBeanFactoryPostProcessors(beanFactory);// Register bean processors that intercept bean creation.registerBeanPostProcessors(beanFactory);// Initialize message source for this context.initMessageSource();// Initialize event multicaster for this context.initApplicationEventMulticaster();// Initialize other special beans in specific context subclasses.onRefresh();// Check for listener beans and register them.registerListeners();// Instantiate all remaining (non-lazy-init) singletons.finishBeanFactoryInitialization(beanFactory);// Last step: publish corresponding event.finishRefresh();}catch (BeansException ex) {if (logger.isWarnEnabled()) {logger.warn("Exception encountered during context initialization - " +"cancelling refresh attempt: " + ex);}// Destroy already created singletons to avoid dangling resources.destroyBeans();// Reset 'active' flag.cancelRefresh(ex);// Propagate exception to caller.throw ex;}finally {// Reset common introspection caches in Spring's core, since we// might not ever need metadata for singleton beans anymore...resetCommonCaches();}}

 protected void invokeBeanFactoryPostProcessors(ConfigurableListableBeanFactory beanFactory) {// 调用bean工厂的后置处理器，getBeanFactoryPostProcessors（）获取当前后端后置处理器PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(beanFactory, getBeanFactoryPostProcessors());// loadTimeWeave逻辑if (beanFactory.getTempClassLoader() == null && beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));}}

调用beanFactoryPostProcessor的核心实现，注意 BeanDefinitionRegistryPostProcessor是BeanFactoryPostProcessor的一个实现

public static void invokeBeanFactoryPostProcessors(ConfigurableListableBeanFactory beanFactory, List<BeanFactoryPostProcessor> beanFactoryPostProcessors) {// 存放处理过的beanSet<String> processedBeans = new HashSet<>();// 如果bean工厂实现了 BeanDefinitionRegistry 需要进行 BeanDefinitionRegistryPostProcessor 后置处理器逻辑,这里beanFactory是一个BeanDefinitionRegistryif (beanFactory instanceof BeanDefinitionRegistry) {BeanDefinitionRegistry registry = (BeanDefinitionRegistry) beanFactory;// 存放普通的BeanFactoryPostProcessorList<BeanFactoryPostProcessor> regularPostProcessors = new ArrayList<>();// 存放了实现 BeanDefinitionRegistryPostProcessor// BeanDefinitionRegistryPostProcessor接口是BeanFactoryPostProcessor的一个子接口// 在其中定义了 postProcessBeanDefinitionRegistry(BeanDefinitionRegistry registry) 方法，在普通的bean定义信息加载完成后，在初始化bean之前允许进一步添加Definition处理。List<BeanDefinitionRegistryPostProcessor> registryProcessors = new ArrayList<>();// 调用beanFactory中现在已经有的BeanFactoryPostProcessor的方法for (BeanFactoryPostProcessor postProcessor : beanFactoryPostProcessors) {if (postProcessor instanceof BeanDefinitionRegistryPostProcessor) {BeanDefinitionRegistryPostProcessor registryProcessor =(BeanDefinitionRegistryPostProcessor) postProcessor;        // 添加之前首先调用一个bean定义信息后置处理器的方法registryProcessor.postProcessBeanDefinitionRegistry(registry);// BeanDefinitionRegistryPostProcessor添加registryProcessors.add(registryProcessor);}else {// 普通的beanFactoryPostProcessor添加regularPostProcessors.add(postProcessor);}}// 实现调用的优先级逻辑，实现了PriorityOrdered，Ordered接口的优先调用。// 这整个优先级处理逻辑，获取BeanDefinitionRegistryPostProcessor的信息，根据优先级，getBean创建实例，然后调用BeanDefinitionRegistryPostProcessor的方法List<BeanDefinitionRegistryPostProcessor> currentRegistryProcessors = new ArrayList<>();// 拿到实现了PriorityOrdered接口的 BeanDefinitionRegistryPostProcessor进行调用// 这里忽略beanFactory.getBean 获取bean实例的过程String[] postProcessorNames =beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);for (String ppName : postProcessorNames) {if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));processedBeans.add(ppName);}}sortPostProcessors(currentRegistryProcessors, beanFactory);registryProcessors.addAll(currentRegistryProcessors);invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);currentRegistryProcessors.clear();// 拿到实现了Ordered接口的 BeanDefinitionRegistryPostProcessor进行调用postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);for (String ppName : postProcessorNames) {if (!processedBeans.contains(ppName) && beanFactory.isTypeMatch(ppName, Ordered.class)) {currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));processedBeans.add(ppName);}}sortPostProcessors(currentRegistryProcessors, beanFactory);registryProcessors.addAll(currentRegistryProcessors);invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);currentRegistryProcessors.clear();// 调用剩余的 BeanDefinitionRegistryPostProcessors boolean reiterate = true;while (reiterate) {reiterate = false;postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);for (String ppName : postProcessorNames) {if (!processedBeans.contains(ppName)) {currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));processedBeans.add(ppName);reiterate = true;}}sortPostProcessors(currentRegistryProcessors, beanFactory);registryProcessors.addAll(currentRegistryProcessors);invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);currentRegistryProcessors.clear();}// 调用BeanFactoryPostProcessor处理逻辑invokeBeanFactoryPostProcessors(registryProcessors, beanFactory);invokeBeanFactoryPostProcessors(regularPostProcessors, beanFactory);}else {// beanFactory不是一个beanDefinitionRegistry那么也是直接调用beanFactoryPostProcessor的方法invokeBeanFactoryPostProcessors(beanFactoryPostProcessors, beanFactory);}// 获取或有BeanFactoryPostProcessor，又是一样的套路，先调用实现了优先级的，然后在调用普通的。BeanFactoryPostProcessor。String[] postProcessorNames =beanFactory.getBeanNamesForType(BeanFactoryPostProcessor.class, true, false);List<BeanFactoryPostProcessor> priorityOrderedPostProcessors = new ArrayList<>();List<String> orderedPostProcessorNames = new ArrayList<>();List<String> nonOrderedPostProcessorNames = new ArrayList<>();for (String ppName : postProcessorNames) {if (processedBeans.contains(ppName)) {// skip - already processed in first phase above}else if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {priorityOrderedPostProcessors.add(beanFactory.getBean(ppName, BeanFactoryPostProcessor.class));}else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {orderedPostProcessorNames.add(ppName);}else {nonOrderedPostProcessorNames.add(ppName);}}// First, invoke the BeanFactoryPostProcessors that implement PriorityOrdered.sortPostProcessors(priorityOrderedPostProcessors, beanFactory);invokeBeanFactoryPostProcessors(priorityOrderedPostProcessors, beanFactory);// Next, invoke the BeanFactoryPostProcessors that implement Ordered.List<BeanFactoryPostProcessor> orderedPostProcessors = new ArrayList<>();for (String postProcessorName : orderedPostProcessorNames) {orderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));}sortPostProcessors(orderedPostProcessors, beanFactory);invokeBeanFactoryPostProcessors(orderedPostProcessors, beanFactory);// Finally, invoke all other BeanFactoryPostProcessors.List<BeanFactoryPostProcessor> nonOrderedPostProcessors = new ArrayList<>();for (String postProcessorName : nonOrderedPostProcessorNames) {nonOrderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));}invokeBeanFactoryPostProcessors(nonOrderedPostProcessors, beanFactory);// Clear cached merged bean definitions since the post-processors might have// modified the original metadata, e.g. replacing placeholders in values...beanFactory.clearMetadataCache();}

Spring容器创建流程（4）调用beanFactory后置处理器相关推荐

Spring容器创建流程——总结
spring容器创建的主要流程在他的refresh()方法中,接下来就开始总结一个下他的refresh()方法中的每个步骤大概都做了那些事情.refresh() 可在AbstractApplicati ...
Spring源码|解析深入Spring源码多图剖析@Configuration背后的BeanFactory后置处理器实现逻辑
揭秘@Configuration的秘密之BeanFactory后置处理器前序文章 Spring如何扫描工作目录下的Bean?|图文并茂讲解@Configuration的工作原理文章目录揭秘@Co ...
Spring容器创建流程（5）bean后置处理之注册
registerBeanPostProcessors 注册bean的后置处理器(以前的执行流程可在系列文章中查看),注意 beanFactoryPostProcessor 是 bean工厂的后置处理器 ...
spring系列-注解驱动原理及源码-spring容器创建流程
目录一.spring容器的refresh()[创建刷新] 二.BeanFactory 的创建及预准备工作 1.prepareRefresh()刷新前预处理工作. 2.obtainFreshBeanF ...
Spring容器创建流程（8）初始化bean
finishBeanFactoryInitialization(beanFactory); 很重要的一步,初始化剩余未初始化的bean(还没有创建实例放到容器中的). 容器refresh总览: syn ...
Spring容器创建流程（9）完成创建
Spring的refresh() 方法中finishRefresh()方法完成之后也就代表着,Spring容器真正的创建完成了.下面看finishRefresh()的源码. 容器refresh总览: ...
Spring容器创建流程（7）事件派发机制
Spring事件驱动,监听机制.由三步分组成,事件,派发器,监听器. 事件: spring事件的顶级父类是EventObject,通常情况下继承ApplicationEvent 自定义自己的事件. 事 ...
Spring容器创建流程（6）国际化支持
initMessageSource 初始化MessageSource,Spring国际化支持(之前的执行步骤可在系列文章中找到) 容器refresh总览: synchronized (this.sta ...
Spring容器创建流程（1）容器创建准备
本系列文章将逐一介绍,Spring容器创建到容器刷新完成每个过程. Spring容器继承结构图第一步,new容器实例 ApplicationContext factory = new ClassPa ...

Spring容器创建流程（4）调用beanFactory后置处理器

Spring容器创建流程（4）调用beanFactory后置处理器相关推荐

最新文章

热门文章