Spring 5 AbstractBeanFactory -- createBean 源码解析(一)

Spring 5 AbstractBeanFactory – createBean 源码解析(一)
Spring 5 AbstractBeanFactory – createBean 源码解析(二)

相关源码注释

ApplicationContext

Spring 5 DefaultResourceLoader 源码注释
Spring 5 AbstractApplicationContext 源码注释

BeanFactory

Spring 5 SimpleAliasRegistry 源码注释
Spring 5 DefaultSingletonBeanRegistry 源码注释
Spring 5 FactoryBeanRegistrySupport 源码注释
Spring 5 AbstractBeanFactory 源码注释
Spring 5 AbstractAutowireCapableBeanFactory 源码注释
Spring 5 DefaultLisbaleBeanFactory 源码注释

createBean

为给定的合并后BeanDefinition(和参数)创建一个bean实例.
这是一个抽象方法。

/**
	 * Create a bean instance for the given merged bean definition (and arguments).
	 * <p>为给定的合并后BeanDefinition(和参数)创建一个bean实例</p>
	 * The bean definition will already have been merged with the parent definition
	 * in case of a child definition.
	 * <p>如果是子定义，则BeanDefinition将已经与父定义合并</p>
	 * <p>All bean retrieval methods delegate to this method for actual bean creation.
	 * <p>所有bean检索方法都委托方法进行实际的bean创建</p>
	 * @param beanName the name of the bean -- bean名
	 * @param mbd the merged bean definition for the bean -- bean的合并后BeanDefinition
	 * @param args explicit arguments to use for constructor or factory method invocation
	 *             -- 用于构造函数或工厂方法调用的显示参数
	 * @return a new instance of the bean -- Bean新实例
	 * @throws BeanCreationException if the bean could not be created -- 如果无法创建该bean
	 */
	protected abstract Object createBean(String beanName, RootBeanDefinition mbd, @Nullable Object[] args)
			throws BeanCreationException;

由 AbstractAutowireCapableBeanFactory 实现.

/**
	 * Central method of this class: creates a bean instance,
	 * populates the bean instance, applies post-processors, etc.
	 * <p>此类的重要方法：创建Bean实例，填充Bean实例，应用后处理器等</p>
	 * @see #doCreateBean
	 */
	@Override
	protected Object createBean(String beanName, RootBeanDefinition mbd, @Nullable Object[] args)
			throws BeanCreationException {

		//如果开启跟踪级别日志
		if (logger.isTraceEnabled()) {
			//打印跟踪日志 ： 创建bean的实例'beanName'
			logger.trace("Creating instance of bean '" + beanName + "'");
		}
		//mbd的深度副本
		RootBeanDefinition mbdToUse = mbd;

		// Make sure bean class is actually resolved at this point, and
		// clone the bean definition in case of a dynamically resolved Class
		// which cannot be stored in the shared merged bean definition.
		// 确保此时确实解析了bean类，并在无法动态存储的Class不能存储在共享合并后
		// BeanDefinition中的情况下克隆beanDefinition

		//为mdb解析出对应的bean class
		Class<?> resolvedClass = resolveBeanClass(mbd, beanName);
		//如果成功解析出Class 且 mbd没有指定了bean类 且 mbd配置了bean类名
		if (resolvedClass != null && !mbd.hasBeanClass() && mbd.getBeanClassName() != null) {
			//创建一个新的RootBeanDefinition作为mbd的深层副本
			mbdToUse = new RootBeanDefinition(mbd);
			//将解析出来的reolvedClass设置到mbd副本里
			mbdToUse.setBeanClass(resolvedClass);
		}

		// Prepare method overrides.
		// 准备方法替代
		try {
			//验证并准备mbdToUse的方法替换。检查是否存在具有指定名称的方法。
			mbdToUse.prepareMethodOverrides();
		}
		//捕捉BeanDefinition验证失败时引发的异常
		catch (BeanDefinitionValidationException ex) {
			//Bean定义存储异常：beanName,验证失败
			throw new BeanDefinitionStoreException(mbdToUse.getResourceDescription(),
					beanName, "Validation of method overrides failed", ex);
		}

		try {
			// Give BeanPostProcessors a chance to return a proxy instead of the target bean instance.
			// 给BeanPostProcessors一个返回代理而不是目标bean实例的机会
			//应用InstantiationAwareBeanPostProcessor后处理器实例化benName的实例对象
			Object bean = resolveBeforeInstantiation(beanName, mbdToUse);
			//如果成功获取到了实例对象
			if (bean != null) {
				//直接返回这个实例对象
				return bean;
			}
		}
		catch (Throwable ex) {
			//抛出Bean创建异常:Bean实例化之前的BeanPostProcess失败
			throw new BeanCreationException(mbdToUse.getResourceDescription(), beanName,
					"BeanPostProcessor before instantiation of bean failed", ex);
		}

		try {
			//实际创建Bean的方法
			Object beanInstance = doCreateBean(beanName, mbdToUse, args);
			//如果日志级别是跟踪
			if (logger.isTraceEnabled()) {
				//打印跟踪日志：完成创建Bean的创建
				logger.trace("Finished creating instance of bean '" + beanName + "'");
			}
			//返回bean实例
			return beanInstance;
		}
		catch (BeanCreationException | ImplicitlyAppearedSingletonException ex) {//捕捉Bean创建异常|隐式出现的单例异常
			// A previously detected exception with proper bean creation context already,
			// or illegal singleton state to be communicated up to DefaultSingletonBeanRegistry.
			// 之前检测到的异常已经带有正确的bean创建上下文，或者非法的单例状态要传递给 DefaultSingletonBeanRegistry
			//重新抛出ex
			throw ex;
		}
		catch (Throwable ex) {//捕捉创建Bean出现的所有异常
			//抛出Bean创建异常：创建Bean期间的意外异常
			throw new BeanCreationException(
					mbdToUse.getResourceDescription(), beanName, "Unexpected exception during bean creation", ex);
		}
	}

resolveBeanClass(mbd, beanName);

Spring 5 AbstractBeanFactory – resolveBeanClass源码解析

resolveBeforeInstantiation(beanName, mbdToUse)

应用InstantiationAwareBeanPostProcessor后处理器实例化benName的实例对象：

1. 定义一个【变量bean】默认为null，表示没有InstantiationAwareBeanPostProcessor后处理器 可实例化beanName的实例对象
2. 如果mdb还没有启动实例化前的后处理器【RootBeanDefinition#beforeInstantiationResolved】：
   1. 如果mbd不是合成的 且 该工厂拥有InstiationAwareBeanPostProcessor:
      1. 确定mbd的目标类型，【变量targetType】
      2. 如果成功获取到了targetType:
         1. 在实例化之前应用 InstantiationAwareBeanPostProcessor 后处理器,并尝试通过BeanPostProcess创建 beanName&beanClass的单例对象 【变量 bean】
         2. 如果成功获取bean,就应用所有BeanPostProcess对bean进行后处理包装。
   2. 当bean实例化成功后，对mbd加上已启动实例化前的后处理器的标记【RootBeanDefinition#beforeInstantiationResolved】
3. 返回bean

/**
	 * Apply before-instantiation post-processors, resolving whether there is a
	 * before-instantiation shortcut for the specified bean.
	 * <p>应用实例化之前的后处理器，以解决指定的bean是否存在实例化快捷方式</p>
	 * @param beanName the name of the bean --bean名
	 * @param mbd the bean definition for the bean -- bean的合并后BeanDefinition
	 * @return the shortcut-determined bean instance, or {@code null} if none
	 *  -- 快捷方式确定的bean实例；如果没有，则未null
	 */
	@Nullable
	protected Object resolveBeforeInstantiation(String beanName, RootBeanDefinition mbd) {
		//定义一个变量bean，默认为null，表示没有InstantiationAwareBeanPostProcessor后处理器可实例化beanName的实例对象
		Object bean = null;
		//如果mdb还没有启动实例化前的后处理器
		if (!Boolean.FALSE.equals(mbd.beforeInstantiationResolved)) {
			// Make sure bean class is actually resolved at this point.
			// 确保此时确实解决了bean类
			//如果mbd不是合成的 且 该工厂拥有InstiationAwareBeanPostProcessor
			if (!mbd.isSynthetic() && hasInstantiationAwareBeanPostProcessors()) {
				//确定mbd的目标类型
				Class<?> targetType = determineTargetType(beanName, mbd);
				//如果成功获取到了目标类型
				if (targetType != null) {
					//在实例化之前应用 InstantiationAwareBeanPostProcessor 后处理器,并尝试通过Bean后处理器创建beanName&beanClass的单例对象
					bean = applyBeanPostProcessorsBeforeInstantiation(targetType, beanName);
					//如果成功获取单例对象
					if (bean != null) {
						//在实例化之后，应用所有BeanPostProcess对bean进行后处理包装。
						bean = applyBeanPostProcessorsAfterInitialization(bean, beanName);
					}
				}
			}
			//当bean实例化成功后，对mbd加上已启动实例化前的后处理器的标记
			mbd.beforeInstantiationResolved = (bean != null);
		}
		return bean;
	}

hasInstantiationAwareBeanPostProcessors()

返回此工厂是否拥有InstiationAwareBeanPostProcessor，它将在关闭时应用于单例bean

/**
	 * Indicates whether any InstantiationAwareBeanPostProcessors have been registered.
	 * <p>指示是否已经注册了任何 InstantiationAwareBeanPostProcessors 对象</p>
	 * */
	private volatile boolean hasInstantiationAwareBeanPostProcessors;
	
	/**
	 * Return whether this factory holds a InstantiationAwareBeanPostProcessor
	 * that will get applied to singleton beans on shutdown.
	 * <p>返回此工厂是否拥有InstiationAwareBeanPostProcessor，它将在关闭时应用于单例bean</p>
	 * @see #addBeanPostProcessor
	 * @see org.springframework.beans.factory.config.InstantiationAwareBeanPostProcessor
	 */
	protected boolean hasInstantiationAwareBeanPostProcessors() {
		return this.hasInstantiationAwareBeanPostProcessors;
	}

determineTargetType(beanName, mbd);

确定给定的bean定义的目标类型：

1. 从mbd中获取目标类型【targetType】,获取成功就返回
2. 如果bean的合并定义中有设置工厂方法名，就通过工厂方法区解析出targetType
3. 否则调用resolveBeanClass(mbd, beanName, typesToMatch))解析出targetType
4. 如果typeToMatch为空数组 或者 该工厂没有临时类加载器,缓存解析出来的targetType到mbd中，以免重新解析.
5. 返回targetType

	/**
	 * Determine the target type for the given bean definition.
	 * <p>确定给定的bean定义的目标类型</p>
	 * @param beanName the name of the bean (for error handling purposes) -- bean名(用于错误处理）
	 * @param mbd the merged bean definition for the bean -- bean的合并bean定义
	 * @param typesToMatch the types to match in case of internal type matching purposes
	 * (also signals that the returned {@code Class} will never be exposed to application code)
	 *     -- 如果要进行内部类型匹配，则要进行匹配（也表明返回Class永远不会暴露给应用程序代码）
	 * @return the type for the bean if determinable, or {@code null} otherwise
	 * 	--	Bean的类型（如果可以确定的话），否则为 null
	 */
	@Nullable
	protected Class<?> determineTargetType(String beanName, RootBeanDefinition mbd, Class<?>... typesToMatch) {
		//获取bean的合并定义的目标类型
		Class<?> targetType = mbd.getTargetType();
		//如果没有成功获取到目标类型
		if (targetType == null) {
			//如果bean的合并定义中有设置工厂方法名，就通过工厂方法区解析出targetType,否则
			//交给resolveBeanClass方法解析出targetType
			targetType = (mbd.getFactoryMethodName() != null ?
					getTypeForFactoryMethod(beanName, mbd, typesToMatch) :
					resolveBeanClass(mbd, beanName, typesToMatch));
			//如果typeToMatch为空数组 或者 该工厂没有临时类加载器
			if (ObjectUtils.isEmpty(typesToMatch) || getTempClassLoader() == null) {
				//缓存解析出来的targetType到mbd中，以免重新解析
				mbd.resolvedTargetType = targetType;
			}
		}
		return targetType;
	}

getTypeForFactoryMethod(beanName, mbd, typesToMatch)

Spring 5 AbstractAutowireCapableBeanFactory-- getTypeForFactoryMethod源码解析

resolveBeanClass(mbd, beanName, typesToMatch)

Spring 5 AbstractBeanFactory – resolveBeanClass源码解析

applyBeanPostProcessorsBeforeInstantiation(targetType, beanName);

在实例化之前应用Bean后处理器,并尝试通过Bean后处理器创建beanName&beanClass的单例对象

1. 遍历该工厂创建的bean的BeanPostProcessors列表,元素为bp:
   1. 如果 bp 是 InstantiationAwareBeanPostProcessor 的实例:
      1. 将 bp 强转为InstantiationAwareBeanPostProcessor对象
      2. 调用postProcessBeforeInstantiation方法得到beanName指定的实例对象
      3. 如果该实例对象获取成功,直接返回该实例对象
2. 返回null，表示该beanClass/beanName未能通过InstantiationAwareBeanPostProcessor实例化出指定实例对象

/**
	 * Apply InstantiationAwareBeanPostProcessors to the specified bean definition
	 * (by class and name), invoking their {@code postProcessBeforeInstantiation} methods.
	 * <p>将 InstantiationAwareBeanPostProcessors 应用于指定的beanDefinition(按类和名称),并
	 * 调用他们的 postProcessBeforeInstantiation 方法</p>
	 * <p>Any returned object will be used as the bean instead of actually instantiating
	 * the target bean. A {@code null} return value from the post-processor will
	 * result in the target bean being instantiated.
	 * <p>任何返回的对象都将用做bean，而不是实际实例化目标bean。后置处理器返回的空值将导致目标bean
	 * 被实例化。</p>
	 * @param beanClass the class of the bean to be instantiated -- 要实例化的bean类型
	 * @param beanName the name of the bean -- bean名
	 * @return the bean object to use instead of a default instance of the target bean, or {@code null}
	 *  -- 要使用bean的bean对象，而不是目标的默认实例，或 null
	 * @see InstantiationAwareBeanPostProcessor#postProcessBeforeInstantiation
	 */
	@Nullable
	protected Object applyBeanPostProcessorsBeforeInstantiation(Class<?> beanClass, String beanName) {
		//遍历该工厂创建的bean的BeanPostProcessors列表
		for (BeanPostProcessor bp : getBeanPostProcessors()) {
			//如果 bp 是 InstantiationAwareBeanPostProcessor 的实例
			if (bp instanceof InstantiationAwareBeanPostProcessor) {
				//将 bp 强转为InstantiationAwareBeanPostProcessor对象
				InstantiationAwareBeanPostProcessor ibp = (InstantiationAwareBeanPostProcessor) bp;
				//调用postProcessBeforeInstantiation方法得到beanName指定的实例对象
				Object result = ibp.postProcessBeforeInstantiation(beanClass, beanName);
				//如果该实例对象获取成功
				if (result != null) {
					//也就是说如果出现多个InstantiationAwareBeanPostProcessor实例都可对beanName进行创建
					//其实例对象，也是会按照BeanPostProcessors列表的顺序，谁第一个被调用就用谁。
					//直接返回出去
					return result;
				}
			}
		}
		//返回null，表示该beanClass/beanName未能通过InstantiationAwareBeanPostProcessor实例化出指定实例对象
		return null;
	}

applyBeanPostProcessorsAfterInitialization(bean, beanName);

对 existingBean 进行初始化后的后处理:

1. 初始化结果对象为result,默认引用existingBean
2. 遍历该工厂创建的bean的BeanPostProcessors列表:
   1. 回调BeanPostProcessor#postProcessAfterInitialization来对result进行包装【变量 current】
   2. 如果current为null,直接返回result，中断其后续的BeanPostProcessor处理
   3. 让result引用current,使其经过所有BeanPostProcess对象的后置处理的层层包装
3. 返回经过所有BeanPostProcess对象的后置处理的层层包装后的result

/**
	 * @param existingBean the existing bean instance -- 现有的bean实例
	 * @param beanName the name of the bean, to be passed to it if necessary
	 * (only passed to {@link BeanPostProcessor BeanPostProcessors};
	 * can follow the {@link #ORIGINAL_INSTANCE_SUFFIX} convention in order to
	 * enforce the given instance to be returned, i.e. no proxies etc)
	 * Bean名称，必要时将传递给它(仅传递给BeanPostProcessor;可以遵循ORIGINAL_INSTANCE_SUFFIX
	 * 约定以强制返回给定的实例,即没有代理等)
	 * @return
	 * @throws BeansException
	 */
	@Override
	public Object applyBeanPostProcessorsAfterInitialization(Object existingBean, String beanName)
			throws BeansException {
		//初始化结果对象为result，默认引用existingBean
		Object result = existingBean;
		//遍历该工厂创建的bean的BeanPostProcessors列表
		for (BeanPostProcessor processor : getBeanPostProcessors()) {
			//回调BeanPostProcessor#postProcessAfterInitialization来对现有的bean实例进行包装
			Object current = processor.postProcessAfterInitialization(result, beanName);
			//一般processor对不感兴趣的bean会回调直接返回result，使其能继续回调后续的BeanPostProcessor；
			// 但有些processor会返回null来中断其后续的BeanPostProcessor
			//如果current为null
			if (current == null) {
				//直接返回result，中断其后续的BeanPostProcessor处理
				return result;
			}
			//让result引用processor的返回结果,使其经过所有BeanPostProcess对象的后置处理的层层包装
			result = current;
		}
		//返回经过所有BeanPostProcess对象的后置处理的层层包装后的result
		return result;
	}

doCreateBean(beanName, mbdToUse, args);

实际创建指定的bean:

1. 使用适当的实例化策略为指定的Bean创建一个新实例：工厂方法，构造函数自动装配或简单实例化
2. 将 工厂中的所有 MergedBeanDefinitionPostProcessors 应用到mbd ,调用这些后处理器 的 postProcessMergedBeanDefinition 方法
3. 用来自 BeanDefinition的属性值填充instanceWrapper中的bean实例
4. 初始化给定的Bean实例，应用工厂回调以及init方法和BeanPostProcessors
5. 将bean添加到该工厂中的可丢弃Bean列表中，注册器可丢弃Bean接口 和/或 在工厂关闭 时调用给

/**
	 * Cache of unfinished FactoryBean instances: FactoryBean name to BeanWrapper.
	 * <p>未完成的FactoryBean实例的高速缓存：FactoryBean名-BeanWrapper</p>
	 * */
	private final ConcurrentMap<String, BeanWrapper> factoryBeanInstanceCache = new ConcurrentHashMap<>();
	/**
	 * Whether to automatically try to resolve circular references between beans.
	 * <p>是否尝试自动解决Bean之间的循环引用。</p>
	 * <p>循环引用的意思是：A引用了B,B引用了C,C又引用了A</p>
	 * */
	private boolean allowCircularReferences = true;

/**
	 * Actually create the specified bean. Pre-creation processing has already happened
	 * at this point, e.g. checking {@code postProcessBeforeInstantiation} callbacks.
	 * <p>实际创建指定的bean。此时，预创建处理已经发生，例如检查postProcessBeforeInstantiation回调。</p>
	 * <p>Differentiates between default bean instantiation, use of a
	 * factory method, and autowiring a constructor.
	 * <p>在默认bean实例化,使用工厂方法和自动装配构造函数之间进行区分</p>
	 * @param beanName the name of the bean --bean名
	 * @param mbd the merged bean definition for the bean -- 合并后的beanDefinition
	 * @param args explicit arguments to use for constructor or factory method invocation
	 *             -- 用于构造函数或工厂方法调用的显示参数
	 * @return a new instance of the bean -- bean新实例
	 * @throws BeanCreationException if the bean could not be created -- 如果无法创建bean
	 * @see #instantiateBean
	 * @see #instantiateUsingFactoryMethod
	 * @see #autowireConstructor
	 */
	protected Object doCreateBean(final String beanName, final RootBeanDefinition mbd, final @Nullable Object[] args)
			throws BeanCreationException {

		// Instantiate the bean.
		//实例化bean
		//BeanWrapper是对Bean的包装，其接口中所定义的功能很简单包括设置获取被包装的对象，
		// 获取被包装bean的属性描述器，由于BeanWrapper接口是PropertyAccessor的子接口，
		// 因此其也可以设置以及访问被包装对象的属性值。BeanWrapper大部分情况下是在spring ioc
		// 内部进行使用， 通过BeanWrapper,spring ioc容器可以用统一的方式来访问bean的属性。
		// 用户很少需要直接使用 BeanWrapper进行编程。
		// 实例bean的包装对象
		BeanWrapper instanceWrapper = null;
		//如果mbd配置的时单例作用域
		if (mbd.isSingleton()) {
			//从未完成的FactoryBean实例的高速缓存中移除beanName的BeanWrapper
			instanceWrapper = this.factoryBeanInstanceCache.remove(beanName);
		}
		//如果包装对象获取失败
		if (instanceWrapper == null) {
			//使用适当的实例化策略为指定的Bean创建一个新实例：工厂方法，构造函数自动装配或简单实例化。
			instanceWrapper = createBeanInstance(beanName, mbd, args);
		}
		//获取 instanceWrapperd包装的bean实例
		final Object bean = instanceWrapper.getWrappedInstance();
		//获取 instanceWrapperd包装的bean类型
		Class<?> beanType = instanceWrapper.getWrappedClass();
		//如果beanType不是NullBean
		if (beanType != NullBean.class) {
			//将beanType 缓存到
			mbd.resolvedTargetType = beanType;
		}

		// Allow post-processors to modify the merged bean definition.
		// 允许后处理程序修改合并后的BeanDefinition
		// 使用mbd的后处理器通用锁保证线程安全
		synchronized (mbd.postProcessingLock) {
			//如果mdb没有应用过MergedBeanDefinitionPostProcessor
			if (!mbd.postProcessed) {
				try {
					//将 工厂中的所有 MergedBeanDefinitionPostProcessors 应用到mbd ,调用这些后处理器 的 postProcessMergedBeanDefinition 方法
					applyMergedBeanDefinitionPostProcessors(mbd, beanType, beanName);
				}
				catch (Throwable ex) {
					//捕捉 工厂中的所有 MergedBeanDefinitionPostProcessors应用mbd时的抛出的所有异常，重写抛出Bean创建异常
					throw new BeanCreationException(mbd.getResourceDescription(), beanName,
							"Post-processing of merged bean definition failed", ex);
				}
				//标记该mbd已经应用过 工厂中的所有 MergedBeanDefinitionPostProcessors
				mbd.postProcessed = true;
			}
		}

		// Eagerly cache singletons to be able to resolve circular references
		// even when triggered by lifecycle interfaces like BeanFactoryAware.
		// 饿汉式缓存 单例能够解决 循环依赖，即使被生命周期接口触发。
		// 单例饿汉式暴露的情况标记 = 如果mdb的Bean对象是单例 且 允许自动解决循环依赖问题 且 该beanName正在创建（在整个工厂内）
		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.
		// 初始化Bean实例
		//初始化暴露对象为bean
		Object exposedObject = bean;
		try {
			//用来自 BeanDefinition的属性值填充instanceWrapper中的bean实例
			populateBean(beanName, mbd, instanceWrapper);
			//初始化给定的Bean实例，应用工厂回调以及init方法和BeanPostProcessors
			exposedObject = initializeBean(beanName, exposedObject, mbd);
		}
		catch (Throwable ex) {//捕捉赋值属性，初始化Bean时抛出的任何异常
			//如果ex是属于Bean创建异常 && bean名与ex的异常Bean名一致
			if (ex instanceof BeanCreationException && beanName.equals(((BeanCreationException) ex).getBeanName())) {
				//重新ex
				throw (BeanCreationException) ex;
			}
			else {
				//抛出Bean创建异常：bean的初始化失败
				throw new BeanCreationException(
						mbd.getResourceDescription(), beanName, "Initialization of bean failed", ex);
			}
		}

		//如果是单例饿汉式暴露的情况
		if (earlySingletonExposure) {
			//获取获取以beanName注册的(原始)单例对象，不允许创建早期引用
			Object earlySingletonReference = getSingleton(beanName, false);
			//earlySingletonReference不为null
			if (earlySingletonReference != null) {
				//如果exposedObject与bean是同一个对象
				if (exposedObject == bean) {
					//exposedObject就为 earlySingletonReference
					exposedObject = earlySingletonReference;
				}
				//如果 在循环引用的情况下，不借助注入原始Bean实例，即使注入的Bean最终被包装 && 已经为beanName注册了依赖Bean关系
				else if (!this.allowRawInjectionDespiteWrapping && hasDependentBean(beanName)) {
					//获取依赖于beanName的所有Bean名称
					String[] dependentBeans = getDependentBeans(beanName);
					//定义实际的Bean依赖Set集合，长度与dependentBeans保持一致
					Set<String> actualDependentBeans = new LinkedHashSet<>(dependentBeans.length);
					//遍历dependentBeans
					for (String dependentBean : dependentBeans) {
						//removeSingletonIfCreatedForTypeCheckOnly：删除给定Bean名称的单例实例(如果有的话)，但仅当它没有用于类型检查之外的其他目的时才删除
						//如果没能删除dependentBean
						if (!removeSingletonIfCreatedForTypeCheckOnly(dependentBean)) {
							//将dependentBean添加到 actualDependentBeans
							actualDependentBeans.add(dependentBean);
						}
					}
					//如果actualDependentBeans不为空
					if (!actualDependentBeans.isEmpty()) {
						//抛出Bean当前在创建中异常：名为'BeanName'的Bean在其原始版本中作为循环引用的一部分被注入到其他Bean[actualDependentBeans]中，但
						// 最终被包装了。这意味着其他Bean不适用Bean的最终版本。这通常时过度渴望类型匹配的结果-例如，考虑在关闭'allowEagerInit'标志的
						// 情况下使用'getBeanNamesOfType'
						throw new BeanCurrentlyInCreationException(beanName,
								"Bean with name '" + beanName + "' has been injected into other beans [" +
								StringUtils.collectionToCommaDelimitedString(actualDependentBeans) +
								"] in its raw version as part of a circular reference, but has eventually been " +
								"wrapped. This means that said other beans do not use the final version of the " +
								"bean. This is often the result of over-eager type matching - consider using " +
								"'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.");
					}
				}
			}
		}

createBeanInstance(beanName, mbd, args);

使用适当的实例化策略为指定的Bean创建一个新实例：工厂方法，构造函数自动装配或简单实例化

Spring 5 AbstractAutowireCapableBeanFactory-- createBeanInstance 源码解析

applyMergedBeanDefinitionPostProcessors(mbd, beanType, beanName);

将 MergedBeanDefinitionPostProcessors 应用到指定的 BeanDefinition ,调用它们的 postProcessMergedBeanDefinition 方法

/**
	 * Apply MergedBeanDefinitionPostProcessors to the specified bean definition,
	 * invoking their {@code postProcessMergedBeanDefinition} methods.
	 * <p>将 MergedBeanDefinitionPostProcessors 应用到指定的 BeanDefinition ,调用它们的
	 * postProcessMergedBeanDefinition 方法</p>
	 * @param mbd the merged bean definition for the bean -- bean的合并后beanDefinition
	 * @param beanType the actual type of the managed bean instance -- 托管bean实例的实际类型
	 * @param beanName the name of the bean -- bean名
	 * @see MergedBeanDefinitionPostProcessor#postProcessMergedBeanDefinition
	 */
	protected void applyMergedBeanDefinitionPostProcessors(RootBeanDefinition mbd, Class<?> beanType, String beanName) {
		//遍历工厂创建的bean的BeanPostProcessors列表
		for (BeanPostProcessor bp : getBeanPostProcessors()) {
			// 如果 bp 是 MergedBeanDefinitionPostProcessor 的实例
			if (bp instanceof MergedBeanDefinitionPostProcessor) {
				MergedBeanDefinitionPostProcessor bdp = (MergedBeanDefinitionPostProcessor) bp;
				//回调postProcessMergedBeanDefinition方法，一般MergedBeanDefinitionPostProcessor会做一些 内省BeanDefinition,
				// 	以便对bean 的实际实例进行后处理之前准备一些缓存的元数据，它也可以修改beanDefinition,但只允许用于实际用于并发 修改的Befinition属性。
				// 	本质上，这只适用于在RootBeanDefinition本身定义的操作，而不适用于其基类
				bdp.postProcessMergedBeanDefinition(mbd, beanType, beanName);
			}
		}
	}

isSingletonCurrentlyInCreation(beanName)

返回指定的单例bean当前是否正在创建（在整个工厂内）

/**
		 * Names of beans that are currently in creation.
		 * <p>当前正在创建的bean名称</p>
		 * <p>Collections.newSetFromMap(Map):Collections提供了一种保证元素唯一性的Map实现，
		 * 就是用一个Set来表示Map，它持有这个Map的引用，并且保持Map的顺序、并发和性能特征。</p>
		 *  */
		private final Set<String> singletonsCurrentlyInCreation =
				Collections.newSetFromMap(new ConcurrentHashMap<>(16));
				
/**
	 * Return whether the specified singleton bean is currently in creation
	 * (within the entire factory).
	 * <p>返回指定的单例bean当前是否正在创建（在整个工厂内）</p>
	 * @param beanName the name of the bean - bean名
	 */
	public boolean isSingletonCurrentlyInCreation(String beanName) {
		//从 当前正在创建的bean名称 set集合中判断beanName是否在集合中
		return this.singletonsCurrentlyInCreation.contains(beanName);
	}

篇幅过长，请看下一篇

Spring 5 AbstractBeanFactory – createBean 源码解析(二)