前面已经分析ObtainFreshBeanfactory()这个方法是解析和注册bean,实例化IOC容器的。
重新看一下refresh()方法
@Override
public void refresh() throws BeansException, IllegalStateException {
synchronized (this.startupShutdownMonitor) {
// Prepare this context for refreshing.
prepareRefresh();
// Tell the subclass to refresh the internal bean factory.
**ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();**
// Prepare the bean factory for use in this context.
prepareBeanFactory(beanFactory);
try {
// Allows post-processing of the bean factory in context subclasses.
postProcessBeanFactory(beanFactory);
// Invoke factory processors registered as beans in the context.
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();
}
}
}
接着看prepareBeanFactory()。正如它的API文档上注明的那样,就是配置beanFactory的context的特性包括有context的类加载器,和bean的后置处理器(BeanPostProcessor)。
postProcessBeanFactory():经过标准初始化,修改这个ApplicationContext的内部beanfactory。所有的bean都会被加载(load),但是还没有经过实例化(Initialized)。主要是添加一些自定义的属性,注册BeanPostProcessor。
invokeBeanFactoryPostProcessors():实例化和调用所有注册的BeanFactoryPostProcessor,API文档中标注了必须在 singleton bean的实例化之前调用。BeanFactoryPostProcessor和BeanPostProcessor的区别在于:BeanPostProcessor是在bean 实例化前后增加扩展点,对bean进行一些自定义的逻辑处理。而BeanFactoryPostProcessor从名字上就可以看出这是个Bean的Factory,所以是在Bean实例化之前进行的操作,例如获取bean的定义信息,修改bean的定义信息。而且BeanFactoryPostProcessor可以定义多个,通过添加”order” 这个属性来定义BeanFactoryPostProcessor的执行顺序。举个例子:在处理bean的时候,BeanFactoryPostProcessor修改Bean 的Definitions,然后bean实例化的时候,BeanPostProcessor在实例化前后添加扩展。(注:在设计模式中有个设计原则就是应该对扩展开放,对修改关闭的原则。认为BeanPostProcessor这个恰恰体现了这个原则,BeanPostProcessor中只有两个方法一个postProcessBeforeInitialization是在实例化之前操作逻辑,postProcessAfterInitialization则是在实例化之后操作逻辑,而对中间的实例化不做修改)
registerBeanPostProcessors():实例化和调用所有注册了BeanPostProcessor的Bean,API文档中同样标注了必须在实例化Application beans之前调用。
initMessageSource():实例化消息源工具类
initApplicationEventMulticaster():初始化Spring的事件广播器,下面registerListeners()注册了监听器。事件广播器负责将事件通知给所有的事件监听器。
onRefresh():注册一些特殊的Bean,默认情况下是为空的。
registerListeners():注册所有的监听器,接收initApplicationEventMulticaster广播器通知的事件。
此篇博文到这里就结束了。将在下篇仔细分析下Bean的实例化过程finishBeanFactoryInitialization()。