Spring学习笔记【二】getBean的调用流程

本文参考书籍及部分图片来源自：郝佳编著的Spring源码深度解析

---

前言

对于Bean的加载，Spring是通过getBean实现的，比如：

MyTestBean bean = (MyTestBean)bf.getBean("myTestBean");

@Override
	public Object getBean(String name) throws BeansException {
   
		return doGetBean(name, null, null, false);
	}

从doGetBean中开始整一个getBean的流程，源码中很多方法都有对应它的一个do方法去实现具体操作，接下来我们可以来看看doGetBean具体实现的细节是什么样的。

1.getSingleton可以获取到结果的情况

在最开始的时候会先用 transformedBeanName() 对传入的beanName做转换，因为进来的名称可能是BeanFactory或者别名，如果是BeanFactory就需要去除名字开头的“&”

String beanName = transformedBeanName(name);

接下来就到了比较重要的一个方法——getSingleton(String name)

@Nullable
	protected Object getSingleton(String beanName, boolean allowEarlyReference) {
   
		// Quick check for existing instance without full singleton lock
		Object singletonObject = this.singletonObjects.get(beanName);
		if (singletonObject == null && isSingletonCurrentlyInCreation(beanName)) {
   
			singletonObject = this.earlySingletonObjects.get(beanName);
			if (singletonObject == null && allowEarlyReference) {
   
				synchronized (this.singletonObjects) {
   
					// Consistent creation of early reference within full singleton lock
					singletonObject = this.singletonObjects.get(beanName);
					if (singletonObject == null) {
   
						singletonObject = this.earlySingletonObjects.get(beanName);
						if (singletonObject == null) {
   
							ObjectFactory<?> singletonFactory = this.singletonFactories.get(beanName);
							if (singletonFactory != null) {
   
								singletonObject = singletonFactory.getObject();
								this.earlySingletonObjects.put(beanName, singletonObject);
								this.singletonFactories.remove(beanName);
							}
						}
					}
				}
			}
		}
		return singletonObject;
	}

这段代码首先获取singletonObject，singletonObject是单例池容器，用于缓存创建完成的bean；如果singletonObject不为空说明bean已经创建好，直接返回singletonObject；如果为空并且通过isSingletonCurrentlyInCreation检查是否正在创建中，其中会去判断singletonsCurrentlyInCreation是否contains这个beanName，它是一个Set数组。
接下来看为空判断里做了些什么：
首先会去earlySingletonObjects中获取singletonObject，earlySingletonObjects存有映射bean的早期引用。如果singletonObject不为空说明就直接取出，并返回；如果不为空就对singletonObejcts加锁，准备去singletonFactories获取，如果这时获取得到，就将singletonObject放入earlySingletonObjects中，并remove掉singletonFactories的singletonObject。
这里总结下为什么要使用这段代码：
因为创建单例Bean的时候会存在依赖注入的情况，而创建依赖时为了避免循环依赖的情况，做法就是不等bean创建完成，就把创建bean的ObjectFactory提前曝光（加入到缓存），一旦下个bean需要依赖上个bean时就可以使用上个bean的ObjectFactory。

1.1 getObjectForBeanInstance

如果上文中的singletonObject获取到了就会走到getObjectForBeanInstance方法。

Object sharedInstance = getSingleton(beanName);
if (sharedInstance != null && args == null) {
   
	if (logger.isTraceEnabled()) {
   
		if (isSingletonCurrentlyInCreation(beanName)) {
   
			logger.trace("Returning eagerly cached instance of singleton bean '" + beanName +
							"' that is not fully initialized yet - a consequence of a circular reference");
		}
		else {
   
			logger.trace("Returning cached instance of singleton bean '" + beanName + "'");
		}
	}
	beanInstance = getObjectForBeanInstance(sharedInstance, name, beanName, null);
}

这个方法做的事情就是：Bean的实例化
和上面一样，从代码上解析整个流程：

protected Object getObjectForBeanInstance(
			Object beanInstance, String name, String beanName, @Nullable RootBeanDefinition mbd) {
   

		if (BeanFactoryUtils.isFactoryDereference(name)) {
   
			if (beanInstance instanceof NullBean) {
   
				return beanInstance;
			}
			if (!(beanInstance instanceof FactoryBean)) {
   
				throw new BeanIsNotAFactoryException(beanName, beanInstance.getClass());
			}
			if (mbd != null) {
   
				mbd.isFactoryBean = true;
			}
			return beanInstance;
		}
		if (!(beanInstance instanceof FactoryBean)) {
   
			return beanInstance;
		}

		Object object = null;
		if (mbd != null) {
   
			mbd.isFactoryBean = true;
		}
		else {
   
			object = getCachedObjectForFactoryBean(beanName);
		}
		if (object == null) {
   
			FactoryBean<?> factory = (FactoryBean<?>) beanInstance;
			if (mbd == null && containsBeanDefinition(beanName)) {
   
				mbd = getMergedLocalBeanDefinition(beanName)