Spring底层原理

一块腹肌的门外汉

已于 2024-07-07 15:53:27 修改

阅读量767

点赞数 19

文章标签： java spring

于 2024-04-09 12:30:31 首次发布

本文链接：https://blog.csdn.net/buaixuexideshuge/article/details/137546619

版权

ClassPathXmlApplicationContext启动流程

public ClassPathXmlApplicationContext(
  String[] configLocations, boolean refresh, @Nullable ApplicationContext parent) {
  //调用父类方法创建相关类，对属性的赋值
  super(parent);
  //设置配置
  setConfigLocations(configLocations);
  if (refresh) {
    refresh();
  }
}

setConfigLocations（）

public void setConfigLocations(@Nullable String... locations) {
  if (locations != null) {
    Assert.noNullElements(locations, "Config locations must not be null");
    this.configLocations = new String[locations.length];
    for (int i = 0; i < locations.length; i++) {
      //这里是解析每个给定的路径，例如包含特殊符号的解析（${var}）（可以解析${${}}这种数据）
      this.configLocations[i] = resolvePath(locations[i]).trim();
    }
  }
  else {
    this.configLocations = null;
  }
}

refresh()（核心逻辑）

public void refresh() throws BeansException, IllegalStateException {
  synchronized (this.startupShutdownMonitor) {
    // Prepare this context for refreshing.
    //1、准备刷新上下文环境
    //获取容器的当前时间，同时给容器设置同步标识
    prepareRefresh();
    
    // Tell the subclass to refresh the internal bean factory.
    //2、初始化BeanFactory，并进行XML文件的读取
    ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();
    
    // Prepare the bean factory for use in this context.
    //3、对BeanFactory进行各种功能的填充
    //进入该方法前，Spring已经完成了对配置的解析，而ApplicationContext在功能上的扩展也由此展开
    prepareBeanFactory(beanFactory);
    
    try {
      // Allows post-processing of the bean factory in context subclasses.
      //4、子类覆盖方法做额外的处理
      postProcessBeanFactory(beanFactory);
      
      // Invoke factory processors registered as beans in the context.
      //5、激活各种BeanFactory处理器
      //BeanFactoryPostProcessor接口可以在实例化任何bean之前获取配置信息，从而可以正确解析bean描述文件中的变量引用
      invokeBeanFactoryPostProcessors(beanFactory);
      
      // Register bean processors that intercept bean creation.
      //6、注册拦截Bean创建的Bean处理器（这里只是注册，真正的调用在bean实例化的时候）
      registerBeanPostProcessors(beanFactory);
      
      // Initialize message source for this context.
      //7、为上下文初始化Message源（即不同语言的消息体，国际化处理）
      initMessageSource();
      
      // Initialize event multicaster for this context.
      //8、初始化应用消息广播器
      initApplicationEventMulticaster();
      
      // Initialize other special beans in specific context subclasses.
      //9、留给子类来初始化其它的Bean
      onRefresh();
      
      // Check for listener beans and register them.
      //10、在所有注册的bean中查找Listener bean，并注册到消息广播器中
      registerListeners();
      
      // Instantiate all remaining (non-lazy-init) singletons.
      //11、初始化剩下的单实例（非懒加载的）
      finishBeanFactoryInitialization(beanFactory);
      
      // Last step: publish corresponding event.
      //12、完成刷新过程，通知生命周期处理器lifecycleProcessor刷新过程，
      //同时发出ContextRefreshEvent通知别人
      finishRefresh();
    }
    
    //13、异常之后的处理
    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.
      //重置active标志
      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...
      //14、清除内置缓存
      resetCommonCaches();
    }
  }
}

1.prepareRefresh()准备刷新上下文环境

记录启动开始时间
设置上下文的状态
方法initPropertySources，用户可以自定义属性的处理和设置
对属性进行必要性的校验
初始化监听器及事件集合

protected void prepareRefresh() {
  // Switch to active.
  //记录启动开始时间
  this.startupDate = System.currentTimeMillis();
  //设置Context的当前状态
  this.closed.set(false);
  this.active.set(true);
  
  if (logger.isDebugEnabled()) {
    if (logger.isTraceEnabled()) {
      logger.trace("Refreshing " + this);
    }
    else {
      logger.debug("Refreshing " + getDisplayName());
    }
  }
  
  // Initialize any placeholder property sources in the context environment.
  //初始化上下文环境中的占位符属性来源
  //这个方法是空实现，用户可以根据自身的需要重写该方法，并且在方法中进行个性化的属性处理及设置
  initPropertySources();
  
  // Validate that all properties marked as required are resolvable:
  // see ConfigurablePropertyResolver#setRequiredProperties
  //对属性进行必要的验证，验证需要的属性文件是否都已经放入环境中
  getEnvironment().validateRequiredProperties();
  
  // Store pre-refresh ApplicationListeners...
  if (this.earlyApplicationListeners == null) {
    this.earlyApplicationListeners = new LinkedHashSet<>(this.applicationListeners);
  }
  else {
    // Reset local application listeners to pre-refresh state.
    this.applicationListeners.clear();
    this.applicationListeners.addAll(this.earlyApplicationListeners);
  }
  
  // Allow for the collection of early ApplicationEvents,
  // to be published once the multicaster is available...
  this.earlyApplicationEvents = new LinkedHashSet<>();
}

2.obtainFreshBeanFactory()

创建DefaultListableBeanFactory，并进行配置文件的读取

protected ConfigurableListableBeanFactory obtainFreshBeanFactory() {
    //初始化BeanFactory，并进行XML文件读取，
    //并将得到的BeanFactory记录在当前实体的属性中
    refreshBeanFactory();
    //返回当前实体的BeanFactory属性
    return getBeanFactory();
}

protected final void refreshBeanFactory() throws BeansException {
  //如果容器已经存在一个BeanFactory，则对其进行销毁和关闭
  if (hasBeanFactory()) {
    //銷毀单例bean
    destroyBeans();
    //关闭BeanFactory
    closeBeanFactory();
  }
  try {
    //创建DefaultListableBeanFactory类型的beanFactory
    DefaultListableBeanFactory beanFactory = createBeanFactory();
    //设置序列化Id（目的是为了需要根据Id反序列化出BeanFactory对象）
    beanFactory.setSerializationId(getId());
    //定制beanFactory，设置相关属性
    //包括：
    //（1）是否允许覆盖同名称的不同定义的对象
    //（2）循环依赖
    //（3）设置@Autowared和@Qualifier注解解析器QualifierAnnotationAutowireCandidateResolver
    //子类可以覆盖该方法来进行自定义的设置
    customizeBeanFactory(beanFactory);
    //加载BeanDefinition
    loadBeanDefinitions(beanFactory);
    //使用全局变量记录beanFactory类实例
    synchronized (this.beanFactoryMonitor) {
      this.beanFactory = beanFactory;
    }
  }
  catch (IOException ex) {
    throw new ApplicationContextException("I/O error parsing bean definition source for " + getDisplayName(), ex);
  }
}

protected void customizeBeanFactory(DefaultListableBeanFactory beanFactory) {
    //如果allowBeanDefinitionOverriding不为空，则设置给beanFactory
    //属性含义：是否允许覆盖同名称的不同定义的对象
    if (this.allowBeanDefinitionOverriding != null) {
        beanFactory.setAllowBeanDefinitionOverriding(this.allowBeanDefinitionOverriding);
    }
    //如果allowCircularReferences不为空，则设置给beanFactory
    //属性含义：是否允许bean之间存在循环依赖
    if (this.allowCircularReferences != null) {
        beanFactory.setAllowCircularReferences(this.allowCircularReferences);
    }
}

3.prepareBeanFactory

protected void prepareBeanFactory(ConfigurableListableBeanFactory beanFactory) {
  // Tell the internal bean factory to use the context's class loader etc.
  //设置beanFactory的classLoader为当前context的classLoader
  beanFactory.setBeanClassLoader(getClassLoader());
  //设置beanFactory的表达式语言处理器（Spring 3增加的表达式语言的支持）
  //默认可以使用#{bean.xxx}的形式来调用相关的属性值
  beanFactory.setBeanExpressionResolver(new StandardBeanExpressionResolver(beanFactory.getBeanClassLoader()));
  //创建默认的propertyEditorRegistrar，主要是对bean的属性等设置管理的一个工具（属性编辑器）
  beanFactory.addPropertyEditorRegistrar(new ResourceEditorRegistrar(this, getEnvironment()));
  
  // Configure the bean factory with context callbacks.
  //添加ApplicationContextAwareProcessor
  beanFactory.addBeanPostProcessor(new ApplicationContextAwareProcessor(this));
  
  //设置几个忽略自动装配的接口
  //这些接口会在执行ApplicationContextAwareProcessor时自动装配执行
  beanFactory.ignoreDependencyInterface(EnvironmentAware.class);
  beanFactory.ignoreDependencyInterface(EmbeddedValueResolverAware.class);
  beanFactory.ignoreDependencyInterface(ResourceLoaderAware.class);
  beanFactory.ignoreDependencyInterface(ApplicationEventPublisherAware.class);
  beanFactory.ignoreDependencyInterface(MessageSourceAware.class);
  beanFactory.ignoreDependencyInterface(ApplicationContextAware.class);
  
  // BeanFactory interface not registered as resolvable type in a plain factory.
  // MessageSource registered (and found for autowiring) as a bean.
  //设置几个自动装配的接口
  //一般检测到指定类型的属性，就会自动装配上去
  beanFactory.registerResolvableDependency(BeanFactory.class, beanFactory);
  beanFactory.registerResolvableDependency(ResourceLoader.class, this);
  beanFactory.registerResolvableDependency(ApplicationEventPublisher.class, this);
  beanFactory.registerResolvableDependency(ApplicationContext.class, this);
  
  // Register early post-processor for detecting inner beans as ApplicationListeners.
  beanFactory.addBeanPostProcessor(new ApplicationListenerDetector(this));
  
  // Detect a LoadTimeWeaver and prepare for weaving, if found.
  if (beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
    beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
    // Set a temporary ClassLoader for type matching.
    beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
  }
  
  // Register default environment beans.
  //增加对AspectJ的支持
  if (!beanFactory.containsLocalBean(ENVIRONMENT_BEAN_NAME)) {
    beanFactory.registerSingleton(ENVIRONMENT_BEAN_NAME, getEnvironment());
  }
  //添加默认的系统环境bean
  if (!beanFactory.containsLocalBean(SYSTEM_PROPERTIES_BEAN_NAME)) {
    beanFactory.registerSingleton(SYSTEM_PROPERTIES_BEAN_NAME, getEnvironment().getSystemProperties());
  }
  if (!beanFactory.containsLocalBean(SYSTEM_ENVIRONMENT_BEAN_NAME)) {
    beanFactory.registerSingleton(SYSTEM_ENVIRONMENT_BEAN_NAME, getEnvironment().getSystemEnvironment());
  }
}

4.postProcessBeanFactory(beanFactory);子类覆盖方法做额外的处理

默认空实现，子类可以扩展做一些自定义的处理

5.invokeBeanFactoryPostProcessors(beanFactory);

对于BeanDefinitionRegistry类型的特殊

需要先对所有BeanDefinitionRegistryPostProcessor类型进行postProcessBeanDefinitionRegistry方法触发，再触发BeanFactoryPostProcessor的postProcessBeanFactory方法

非BeanDefinitionRegistry类型

只需要触发BeanFactoryPostProcessor的postProcessBeanFactory方法

在触发BeanDefinitionRegistryPostProcessor和BeanFactoryPostProcessor时，优选触发实现PriorityOrdered类型，其次为Ordered，剩余的最后触发。其中PriorityOrdered和Ordered内部根据配置的数字进行排序触发

PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors
(beanFactory, getBeanFactoryPostProcessors());

// Detect a LoadTimeWeaver and prepare for weaving, if found in the meantime
// (e.g. through an @Bean method registered by ConfigurationClassPostProcessor)
if (beanFactory.getTempClassLoader() == null && beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
  beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
  beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
}

//PostProcessorRegistrationDelegate#invokeBeanFactoryPostProcessors方法
public static void invokeBeanFactoryPostProcessors(
  ConfigurableListableBeanFactory beanFactory, List<BeanFactoryPostProcessor> beanFactoryPostProcessors) {
  
  // Invoke BeanDefinitionRegistryPostProcessors first, if any.
  //记录已经触发的BeanDefinitionRegistryPostProcessors
  Set<String> processedBeans = new HashSet<>();
  
  //对于BeanFactoryPostProcessor的处理分为两种情况
  //（1）对于BeanDefinitionRegistry类型的特殊处理
  //（2）对于普通的BeanFactoryPostProcessor处理
  
  
  //对BeanDefinitionRegistry类型的处理
  if (beanFactory instanceof BeanDefinitionRegistry) {
    BeanDefinitionRegistry registry = (BeanDefinitionRegistry) beanFactory;
    //记录BeanFactoryPostProcessor类型的处理器
    List<BeanFactoryPostProcessor> regularPostProcessors = new ArrayList<>();
    //记录BeanDefinitionRegistryPostProcessor类型的处理器
    List<BeanDefinitionRegistryPostProcessor> registryProcessors = new ArrayList<>();
    
    for (BeanFactoryPostProcessor postProcessor : beanFactoryPostProcessors) {
      //对于BeanDefinitionRegistryPostProcessor类型，需要先调用postProcessBeanDefinitionRegistry方法
      if (postProcessor instanceof BeanDefinitionRegistryPostProcessor) {
        BeanDefinitionRegistryPostProcessor registryProcessor =
          (BeanDefinitionRegistryPostProcessor) postProcessor;
        registryProcessor.postProcessBeanDefinitionRegistry(registry);
        registryProcessors.add(registryProcessor);
      }
      //常规的BeanFactoryPostProcessor
      else {
        regularPostProcessors.add(postProcessor);
      }
    }
    
    // Do not initialize FactoryBeans here: We need to leave all regular beans
    // uninitialized to let the bean factory post-processors apply to them!
    // Separate between BeanDefinitionRegistryPostProcessors that implement
    // PriorityOrdered, Ordered, and the rest.
    List<BeanDefinitionRegistryPostProcessor> currentRegistryProcessors = new ArrayList<>();
    
    // First, invoke the BeanDefinitionRegistryPostProcessors that implement PriorityOrdered.
    // 获取配置文件中配置的且实现PriorityOrdered接口的BeanDefinitionRegistryPostProcessor
    // 填充到currentRegistryProcessors
    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中
    registryProcessors.addAll(currentRegistryProcessors);
    //invoke所有实现PriorityOrdered接口的BeanDefinitionRegistryPostProcessor
    invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
    currentRegistryProcessors.clear();
    
    // Next, invoke the BeanDefinitionRegistryPostProcessors that implement Ordered.
    // 获取配置文件中配置的且实现Ordered接口的BeanDefinitionRegistryPostProcessor
    // 填充到currentRegistryProcessors
    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中
    registryProcessors.addAll(currentRegistryProcessors);
    //invoke所有实现Ordered接口的BeanDefinitionRegistryPostProcessor
    invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
    currentRegistryProcessors.clear();
    
    // Finally, invoke all other BeanDefinitionRegistryPostProcessors until no further ones appear.
    //获取配置文件中配置的剩余的BeanDefinitionRegistryPostProcessor（即未实现任何排序接口）
    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中
      registryProcessors.addAll(currentRegistryProcessors);
      //invoke剩余的BeanDefinitionRegistryPostProcessor（即未实现任何排序接口）
      invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
      currentRegistryProcessors.clear();
    }
    
    // Now, invoke the postProcessBeanFactory callback of all processors handled so far.
    //上面的代码只是触发BeanDefinitionRegistryPostProcessor类型中的postProcessBeanDefinitionRegistry方法，
    //现在需要正式调用postProcessBeanFactory方法
    invokeBeanFactoryPostProcessors(registryProcessors, beanFactory);
    invokeBeanFactoryPostProcessors(regularPostProcessors, beanFactory);
  }
  //普通的beanFactory处理
  else {
    // Invoke factory processors registered with the context instance.
    //对应非BeanDefinitionRegistry类型的beanFactory，直接调用postProcessBeanFactory方法
    invokeBeanFactoryPostProcessors(beanFactoryPostProcessors, beanFactory);
  }
  
  // Do not initialize FactoryBeans here: We need to leave all regular beans
  // uninitialized to let the bean factory post-processors apply to them!
  //获取配置文件里面的所有BeanFactoryPostProcessor类型的实例
  String[] postProcessorNames =
    beanFactory.getBeanNamesForType(BeanFactoryPostProcessor.class, true, false);
  
  // Separate between BeanFactoryPostProcessors that implement PriorityOrdered,
  // Ordered, and the rest.
  //存放实现PriorityOrdered接口的BeanFactoryPostProcessor
  List<BeanFactoryPostProcessor> priorityOrderedPostProcessors = new ArrayList<>();
  //存放实现Ordered接口的BeanFactoryPostProcessor
  List<String> orderedPostProcessorNames = new ArrayList<>();
  //存放剩余的BeanFactoryPostProcessor
  List<String> nonOrderedPostProcessorNames = new ArrayList<>();
  for (String ppName : postProcessorNames) {
    //已经执行过了的BeanFactoryPostProcessor执行跳过
    if (processedBeans.contains(ppName)) {
      // skip - already processed in first phase above
    }
    //实现了PriorityOrdered接口添加到priorityOrderedPostProcessors
    else if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
      priorityOrderedPostProcessors.add(beanFactory.getBean(ppName, BeanFactoryPostProcessor.class));
    }
    //实现了Ordered接口添加到priorityOrderedPostProcessors
    else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
      orderedPostProcessorNames.add(ppName);
    }
    //剩余的（未实现任何排序接口）添加到priorityOrderedPostProcessors
    else {
      nonOrderedPostProcessorNames.add(ppName);
    }
  }
  
  // First, invoke the BeanFactoryPostProcessors that implement PriorityOrdered.
  //首选对实现PriorityOrdered接口的PostProcessor排序
  sortPostProcessors(priorityOrderedPostProcessors, beanFactory);
  //触发
  invokeBeanFactoryPostProcessors(priorityOrderedPostProcessors, beanFactory);
  
  // Next, invoke the BeanFactoryPostProcessors that implement Ordered.
  //其次对实现Ordered接口的PostProcessor排序并触发
  List<BeanFactoryPostProcessor> orderedPostProcessors = new ArrayList<>(orderedPostProcessorNames.size());
  for (String postProcessorName : orderedPostProcessorNames) {
    orderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));
  }
  sortPostProcessors(orderedPostProcessors, beanFactory);
  invokeBeanFactoryPostProcessors(orderedPostProcessors, beanFactory);
  
  // Finally, invoke all other BeanFactoryPostProcessors.
  //最后对剩余的BeanFactoryPostProcessor进行触发
  List<BeanFactoryPostProcessor> nonOrderedPostProcessors = new ArrayList<>(nonOrderedPostProcessorNames.size());
  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();
}

6.registerBeanPostProcessors(beanFactory);

逻辑与注册BeanFactoryPostProcessors很类型，不过这里仅仅是注册，并不触发。且注册的先后顺序为

PriorityOrdered–>Ordered–>无序–>MergedBeanDefinitionPostProcessor，如果既实现了排序接口，又实现了MergedBeanDefinitionPostProcessor接口，则会当做MergedBeanDefinitionPostProcessor来处理

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

    //获取所有的BeanPostProcessor的beanName
    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.
    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
    List<BeanPostProcessor> internalPostProcessors = new ArrayList<>();
    //存放实现Ordered接口的BeanPostProcessor
    List<String> orderedPostProcessorNames = new ArrayList<>();
    //存放无序的BeanPostProcessor
    List<String> nonOrderedPostProcessorNames = new ArrayList<>();
    for (String ppName : postProcessorNames) {
        //如果是实现了PriorityOrdered接口，则加入到priorityOrderedPostProcessors集合中
        if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
            BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
            priorityOrderedPostProcessors.add(pp);
            //如果是MergedBeanDefinitionPostProcessor类型，则继续放入internalPostProcessors集合中
            if (pp instanceof MergedBeanDefinitionPostProcessor) {
                internalPostProcessors.add(pp);
            }
        }
        //如果是实现了Ordered接口，则加入到orderedPostProcessorNames集合中
        else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
            orderedPostProcessorNames.add(ppName);
        }
        //无任何排序规则，则加入到nonOrderedPostProcessorNames集合中
        else {
            nonOrderedPostProcessorNames.add(ppName);
        }
    }

    // First, register the BeanPostProcessors that implement PriorityOrdered.
    //第一步：注册所有实现PriorityOrdered接口的BeanPostProcessor
    //先排序
    sortPostProcessors(priorityOrderedPostProcessors, beanFactory);
    //后注册
    registerBeanPostProcessors(beanFactory, priorityOrderedPostProcessors);

    // Next, register the BeanPostProcessors that implement Ordered.
    //第二步：注册所有实现Ordered接口的BeanPostProcessor
    List<BeanPostProcessor> orderedPostProcessors = new ArrayList<>(orderedPostProcessorNames.size());
    for (String ppName : orderedPostProcessorNames) {
        BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
        orderedPostProcessors.add(pp);
        //如果是MergedBeanDefinitionPostProcessor类型，则继续放入internalPostProcessors集合中
        if (pp instanceof MergedBeanDefinitionPostProcessor) {
            internalPostProcessors.add(pp);
        }
    }
    //排序
    sortPostProcessors(orderedPostProcessors, beanFactory);
    //注册
    registerBeanPostProcessors(beanFactory, orderedPostProcessors);

    // Now, register all regular BeanPostProcessors.
    //第三步：注册所有无序接口的BeanPostProcessor
    List<BeanPostProcessor> nonOrderedPostProcessors = new ArrayList<>(nonOrderedPostProcessorNames.size());
    for (String ppName : nonOrderedPostProcessorNames) {
        BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
        nonOrderedPostProcessors.add(pp);
        //如果是MergedBeanDefinitionPostProcessor类型，则继续放入internalPostProcessors集合中
        if (pp instanceof MergedBeanDefinitionPostProcessor) {
            internalPostProcessors.add(pp);
        }
    }
    //注册
    registerBeanPostProcessors(beanFactory, nonOrderedPostProcessors);

    // Finally, re-register all internal BeanPostProcessors.
    //最后：注册所有MergedBeanDefinitionPostProcessor类型的BeanPostProcessor
    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).
    //添加ApplicationListener探测器
    beanFactory.addBeanPostProcessor(new ApplicationListenerDetector(applicationContext));
}

7.initMessageSource();为上下文初始化Message源（国际化处理）

protected void initMessageSource() {
    ConfigurableListableBeanFactory beanFactory = getBeanFactory();
    if (beanFactory.containsLocalBean(MESSAGE_SOURCE_BEAN_NAME)) {
        this.messageSource = beanFactory.getBean(MESSAGE_SOURCE_BEAN_NAME, MessageSource.class);
        // Make MessageSource aware of parent MessageSource.
        if (this.parent != null && this.messageSource instanceof HierarchicalMessageSource) {
            HierarchicalMessageSource hms = (HierarchicalMessageSource) this.messageSource;
            if (hms.getParentMessageSource() == null) {
                // Only set parent context as parent MessageSource if no parent MessageSource
                // registered already.
                hms.setParentMessageSource(getInternalParentMessageSource());
            }
        }
        if (logger.isTraceEnabled()) {
            logger.trace("Using MessageSource [" + this.messageSource + "]");
        }
    }
    else {
        // Use empty MessageSource to be able to accept getMessage calls.
        DelegatingMessageSource dms = new DelegatingMessageSource();
        dms.setParentMessageSource(getInternalParentMessageSource());
        this.messageSource = dms;
        beanFactory.registerSingleton(MESSAGE_SOURCE_BEAN_NAME, this.messageSource);
        if (logger.isTraceEnabled()) {
            logger.trace("No '" + MESSAGE_SOURCE_BEAN_NAME + "' bean, using [" + this.messageSource + "]");
        }
    }
}

8.initApplicationEventMulticaster();

protected void initApplicationEventMulticaster() {
    ConfigurableListableBeanFactory beanFactory = getBeanFactory();
    //如果用户自定义了事件广播器，那么使用用户自定义的事件广播器
    if (beanFactory.containsLocalBean(APPLICATION_EVENT_MULTICASTER_BEAN_NAME)) {
        this.applicationEventMulticaster =
            beanFactory.getBean(APPLICATION_EVENT_MULTICASTER_BEAN_NAME, ApplicationEventMulticaster.class);
        if (logger.isTraceEnabled()) {
            logger.trace("Using ApplicationEventMulticaster [" + this.applicationEventMulticaster + "]");
        }
    }
    //如果没有定义，则使用默认的SimpleApplicationEventMulticaster
    else {
        this.applicationEventMulticaster = new SimpleApplicationEventMulticaster(beanFactory);
        beanFactory.registerSingleton(APPLICATION_EVENT_MULTICASTER_BEAN_NAME, this.applicationEventMulticaster);
        if (logger.isTraceEnabled()) {
            logger.trace("No '" + APPLICATION_EVENT_MULTICASTER_BEAN_NAME + "' bean, using " +
                         "[" + this.applicationEventMulticaster.getClass().getSimpleName() + "]");
        }
    }
}

9.onRefresh();

默认空实现，子类可以用来初始化其他bean

10.registerListeners();

protected void registerListeners() {
    // Register statically specified listeners first.
    //硬编码方法注册的监听器
    for (ApplicationListener<?> listener : getApplicationListeners()) {
        getApplicationEventMulticaster().addApplicationListener(listener);
    }

    // Do not initialize FactoryBeans here: We need to leave all regular beans
    // uninitialized to let post-processors apply to them!
    //配置文件注册的监听器处理
    String[] listenerBeanNames = getBeanNamesForType(ApplicationListener.class, true, false);
    for (String listenerBeanName : listenerBeanNames) {
        getApplicationEventMulticaster().addApplicationListenerBean(listenerBeanName);
    }

    // Publish early application events now that we finally have a multicaster...
    //触发早期的时间监听器
    Set<ApplicationEvent> earlyEventsToProcess = this.earlyApplicationEvents;
    this.earlyApplicationEvents = null;
    if (earlyEventsToProcess != null) {
        for (ApplicationEvent earlyEvent : earlyEventsToProcess) {
            getApplicationEventMulticaster().multicastEvent(earlyEvent);
        }
    }
}

11.finishBeanFactoryInitialization(beanFactory);

protected void finishBeanFactoryInitialization(ConfigurableListableBeanFactory beanFactory) {
    // Initialize conversion service for this context.
    //初始化一些转换器
    if (beanFactory.containsBean(CONVERSION_SERVICE_BEAN_NAME) &&
        beanFactory.isTypeMatch(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class)) {
        beanFactory.setConversionService(
            beanFactory.getBean(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class));
    }

    // Register a default embedded value resolver if no bean post-processor
    // (such as a PropertyPlaceholderConfigurer bean) registered any before:
    // at this point, primarily for resolution in annotation attribute values.
    //如果没有任何bean post-processor，会默认注入属性解析器
    if (!beanFactory.hasEmbeddedValueResolver()) {
        beanFactory.addEmbeddedValueResolver(strVal -> getEnvironment().resolvePlaceholders(strVal));
    }

    // Initialize LoadTimeWeaverAware beans early to allow for registering their transformers early.
    //初始化LoadTimeWeaverAware类型
    String[] weaverAwareNames = beanFactory.getBeanNamesForType(LoadTimeWeaverAware.class, false, false);
    for (String weaverAwareName : weaverAwareNames) {
        getBean(weaverAwareName);
    }

    // Stop using the temporary ClassLoader for type matching.
    //停止使用临时ClassLoader进行类型匹配
    beanFactory.setTempClassLoader(null);

    // Allow for caching all bean definition metadata, not expecting further changes.
    //冻结所有的bean定义，即bean定义将不被修改或者进行任何一步的处理
    beanFactory.freezeConfiguration();

    // Instantiate all remaining (non-lazy-init) singletons.
    // 实例化所有剩余的（非延迟初始化）单例
    //ApplicationContext默认就是启动时将所有单例bean提前进行实例化
    beanFactory.preInstantiateSingletons();
}

public void preInstantiateSingletons() throws BeansException {
    if (logger.isTraceEnabled()) {
        logger.trace("Pre-instantiating singletons in " + this);
    }

    // Iterate over a copy to allow for init methods which in turn register new bean definitions.
    // While this may not be part of the regular factory bootstrap, it does otherwise work fine.
    List<String> beanNames = new ArrayList<>(this.beanDefinitionNames);

    // Trigger initialization of all non-lazy singleton beans...
    //触发所有非惰性单例bean的初始化
    for (String beanName : beanNames) {
        //获取bean配置信息
        RootBeanDefinition bd = getMergedLocalBeanDefinition(beanName);
        //只加载单例非懒加载的非抽象类
        if (!bd.isAbstract() && bd.isSingleton() && !bd.isLazyInit()) {
            //对应FactoryBean类型的实例的加载
            if (isFactoryBean(beanName)) {
                Object bean = getBean(FACTORY_BEAN_PREFIX + beanName);
                if (bean instanceof FactoryBean) {
                    final FactoryBean<?> factory = (FactoryBean<?>) bean;
                    boolean isEagerInit;
                    if (System.getSecurityManager() != null && factory instanceof SmartFactoryBean) {
                        isEagerInit = AccessController.doPrivileged((PrivilegedAction<Boolean>)
                                                                    ((SmartFactoryBean<?>) factory)::isEagerInit,
                                                                    getAccessControlContext());
                    }
                    else {
                        isEagerInit = (factory instanceof SmartFactoryBean &&
                                       ((SmartFactoryBean<?>) factory).isEagerInit());
                    }
                    if (isEagerInit) {
                        getBean(beanName);
                    }
                }
            }
            //普通bean的加载
            else {
                getBean(beanName);
            }
        }
    }

    // Trigger post-initialization callback for all applicable beans...
    //触发所有bean的初始化后回调
    for (String beanName : beanNames) {
        Object singletonInstance = getSingleton(beanName);
        if (singletonInstance instanceof SmartInitializingSingleton) {
            final SmartInitializingSingleton smartSingleton = (SmartInitializingSingleton) singletonInstance;
            if (System.getSecurityManager() != null) {
                AccessController.doPrivileged((PrivilegedAction<Object>) () -> {
                    smartSingleton.afterSingletonsInstantiated();
                    return null;
                }, getAccessControlContext());
            }
            else {
                smartSingleton.afterSingletonsInstantiated();
            }
        }
    }
}

12.finishRefresh();

protected void finishRefresh() {
    // Clear context-level resource caches (such as ASM metadata from scanning).
    // 清除上下文级别的资源缓存
    clearResourceCaches();

    // Initialize lifecycle processor for this context.
    // 为此上下文初始化生命周期处理器
    initLifecycleProcessor();

    // Propagate refresh to lifecycle processor first.
    //触发所有生命周期处理器的onRefresh方法
    getLifecycleProcessor().onRefresh();

    // Publish the final event.
    //发布上下文刷新事件
    publishEvent(new ContextRefreshedEvent(this));

    // Participate in LiveBeansView MBean, if active.
    LiveBeansView.registerApplicationContext(this);
}

13.resetCommonCaches();

protected void resetCommonCaches() {
    //清除反射使用到的方法和字段缓存
    ReflectionUtils.clearCache();
    //清除注解缓存
    AnnotationUtils.clearCache();
    //清除ResolvableType缓存
    ResolvableType.clearCache();
    //清除ClassLoader缓存
    CachedIntrospectionResults.clearClassLoader(getClassLoader());
}

ClassPathXmlApplicationContext源码解析_classpathxmlapplicationcontext' 不能直接实例化-CSDN博客

继承父类方法，实例化一些属性值

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd">
    <bean id="a" class="com.hs.circulardependency.A" >
        <property name="b" ref="b"></property>
    </bean>
    <bean id="b" class="com.hs.circulardependency.B" >
        <property name="a" ref="a" ></property>
    </bean>
<!--    <bean id="myCycleBeanPostProcessor" class="com.hs.circulardependency.MyCycleBeanPostProcessor">-->

<!--    </bean>-->
</beans>

循环依赖，三级缓存

先创建A对象，在创建A对象时，会先从三级缓存里获取有没有创建过这个对象，没有就开始实例化A对象，实例化完A对象，把A对象存到三级缓存里

给A对象填充属性，这个时候就会涉及B对象，B对象在创建前也会从三级缓存获取数据，没有就实例化B对象，并存到三级缓存里（这个过程和A一样）
接着就是给B填充对象，填充A对象，又会调用到getSingleton这个方法，A对象之前存在三级缓存了，所有能获取到A对象，然后把A对象存到二级缓存里，从三级缓存删除掉