【追根究底】doCreateBean中为什么会对earlySingletonExposure处理两次

==> 学习汇总（持续更新）
==> 从零搭建后端基础设施系列（一）-- 背景介绍

---

• 问题对应的代码片段

  protected Object doCreateBean(final String beanName, final RootBeanDefinition mbd, final @Nullable Object[] args)
  		throws BeanCreationException {
       
  
  	……
  	// Eagerly cache singletons to be able to resolve circular references
  	// even when triggered by lifecycle interfaces like BeanFactoryAware.
  	boolean earlySingletonExposure = (mbd.isSingleton() && this.allowCircularReferences &&
  			isSingletonCurrentlyInCreation(beanName));
  	//第一次处理		
  	if (earlySingletonExposure) {
       
  		if (logger.isTraceEnabled()) {
       
  			logger.trace("Eagerly caching bean '" + beanName +
  					"' to allow for resolving potential circular references");
  		}
  		addSingletonFactory(beanName, () -> getEarlyBeanReference(beanName, mbd, bean));
  	}
  
  	// Initialize the bean instance.
  	Object exposedObject = bean;
  	try {
       
  		populateBean(beanName, mbd, instanceWrapper);
  		exposedObject = initializeBean(beanName, exposedObject, mbd);
  	}
  	catch (Throwable ex) {
       
  		if (ex instanceof BeanCreationException && beanName.equals(((BeanCreationException) ex).getBeanName())) {
       
  			throw (BeanCreationException) ex;
  		}
  		else {
       
  			throw new BeanCreationException(
  					mbd.getResourceDescription(), beanName, "Initialization of bean failed", ex)<