1.6 BeanFactory的后处理
1.6.1激活注册的BeanFactoryPostProcessor
BeanFactoryPostProcessor的用法:
springIOC容器允许BeanFactoryPostProcessor在容器实例实例化任何其他的bean之前读取配置元数据, 并有可能修改它; 并且可以配置多个BeanFactoryPostProcessor,通过"orde"属性控制执行次序;
BeanPostProcesso和BeanFactoryPostProcessor的区别:
- BeanPostProcessor在spring容器实例化bean之后，在执行bean的初始化方法前后，添加一些自己的处理逻辑,BeanPostProcessor是针对bean实例进行修改
- BeanFactoryPostProcessor是在spring容器加载了bean的定义文件之后，在bean实例化之前执行的; BeanFactoryPostProcessor的作用域时容器级的,它只和使用的容器有关; 如果在容器中定义一个BeanFactoryPostProcessor, 它仅仅对此容器中的bean进行后置处理,不会对定义在另一个容器中的bean进行后置处理
- BeanPostProcessor的执行顺序是在BeanFactoryPostProcessor之后
//class PostProcessorRegistrationDelegate {
public static void invokeBeanFactoryPostProcessors( ConfigurableListableBeanFactory beanFactory, List<BeanFactoryPostProcessor> beanFactoryPostProcessors) {
Set<String> processedBeans = new HashSet<String>();
//先判断beanFactory是不是BeanDefinitionRegistry类型，这里的beanFactory是DefaultListableBeanFactory类型实现了BeanDefinitionRegistry接口
if (beanFactory instanceof BeanDefinitionRegistry) {
BeanDefinitionRegistry registry = (BeanDefinitionRegistry) beanFactory;
//regularPostProcessors用来存储BeanFactoryPostProcessor类型
List<BeanFactoryPostProcessor> regularPostProcessors = new LinkedList<BeanFactoryPostProcessor>();
//registryPostProcessors用来存储BeanDefinitionRegistryPostProcessor类型
List<BeanDefinitionRegistryPostProcessor> registryPostProcessors =new LinkedList<BeanDefinitionRegistryPostProcessor>();
/**
* 1.遍历手动注册的BeanFactoryPostProcessor(即硬编码注册的后处理器)
*/
for (BeanFactoryPostProcessor postProcessor : beanFactoryPostProcessors) {
//1.1 验证是否是BeanDefinitionRegistryPostProcessor类型
if (postProcessor instanceof BeanDefinitionRegistryPostProcessor) {
BeanDefinitionRegistryPostProcessor registryPostProcessor =(BeanDefinitionRegistryPostProcessor) postProcessor;
//先去注册自定义后处理器中重写的postProcessBeanDefinitionRegistry方法
registryPostProcessor.postProcessBeanDefinitionRegistry(registry);
//缓存起来
registryPostProcessors.add(registryPostProcessor);
}
//1.2 如果是BeanFactoryPostProcessor类型
else {
regularPostProcessors.add(postProcessor);
}
}
/**
* 2.执行完手动注册的BeanDefinitionRegistryPostProcessor后,查找spring容器中的所有注册了的BeanDefinitionRegistryPostProcessor后置处理器(即配置注册的后处理器)
*/
//在spring容器中得到BeanDefinitionRegistryPostProcessor类型的postProcessorName
String[] postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
//2.1 存储实现了priorityOrdered接口的类
List<BeanDefinitionRegistryPostProcessor> priorityOrderedPostProcessors = new ArrayList<BeanDefinitionRegistryPostProcessor>();
for (String ppName : postProcessorNames) {
//优先执行实现了PriorityOrdered接口的BeanDefinitionRegistryPostProcessor的postProcessBeanDefinitionRegistry方法（按顺序）
if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
//写入存储器
priorityOrderedPostProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));
//存储name表示已经执行
processedBeans.add(ppName);
}
}
//排序
sortPostProcessors(beanFactory, priorityOrderedPostProcessors);
//registryPostProcessors中存储所有的priorityOrderedPostProcessors
registryPostProcessors.addAll(priorityOrderedPostProcessors);
//执行postProcessBeanDefinitionRegistry方法
invokeBeanDefinitionRegistryPostProcessors(priorityOrderedPostProcessors, registry);
postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
//2.2 存储实现了Ordered接口的类
List<BeanDefinitionRegistryPostProcessor> orderedPostProcessors = new ArrayList<BeanDefinitionRegistryPostProcessor>();
for (String ppName : postProcessorNames) {
//执行实现了Ordered接口的BeanDefinitionRegistryPostProcessor的postProcessBeanDefinitionRegistry方法（按顺序）
if (!processedBeans.contains(ppName) && beanFactory.isTypeMatch(ppName, Ordered.class)) {
//存储
orderedPostProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));
//存储name表示已经执行
processedBeans.add(ppName);
}
}
//排序
sortPostProcessors(beanFactory, orderedPostProcessors);
//存储
registryPostProcessors.addAll(orderedPostProcessors);
//执行postProcessBeanDefinitionRegistry方法
invokeBeanDefinitionRegistryPostProcessors(orderedPostProcessors, registry);
//2.3 下面是既没有实现Ordered接口也没有实现PriorityOrdered接口的逻辑
boolean reiterate = true;
while (reiterate) {
reiterate = false;
postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
for (String ppName : postProcessorNames) {
if (!processedBeans.contains(ppName)) {
BeanDefinitionRegistryPostProcessor pp = beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class);
registryPostProcessors.add(pp);
processedBeans.add(ppName);
//执行重写的postProcessBeanDefinitionRegistry方法
pp.postProcessBeanDefinitionRegistry(registry);
reiterate = true;
}
}
}
/**
* 执行registryPostProcessors中对象的postProcessBeanFactory方法
*
* registryPostProcessors集合中存储的是硬编码的+实现了priorityOrdered接口的+实现了Ordered接口的+无序的BeanDefinitionRegistryPostProcessor类型的
*/
invokeBeanFactoryPostProcessors(registryPostProcessors, beanFactory);
/**
* 执行regularPostProcessors中对象的postProcessBeanFactory方法
*
* regularPostProcessors存储的是硬编码的BeanFactoryPostProcessor类型,其他三种类型的在后续的操作中执行
*/
invokeBeanFactoryPostProcessors(regularPostProcessors, beanFactory);
}
else {
invokeBeanFactoryPostProcessors(beanFactoryPostProcessors, beanFactory);
}
/**
* 3.查找spring容器中的所有注册了的BeanFactoryPostProcessor后置处理器
*/
//在spring容器中得到BeanFactoryPostProcessor类型的postProcessorName
String[] postProcessorNames = beanFactory.getBeanNamesForType(BeanFactoryPostProcessor.class, true, false);
//和BeanDefinitionRegistryPostProcessor逻辑一样这里不多说
List<BeanFactoryPostProcessor> priorityOrderedPostProcessors = new ArrayList<BeanFactoryPostProcessor>();
List<String> orderedPostProcessorNames = new ArrayList<String>();
List<String> nonOrderedPostProcessorNames = new ArrayList<String>();
//3.1 对后处理器进行分类
for (String ppName : postProcessorNames) {
if (processedBeans.contains(ppName)) {
//如果已经处理过了,则跳过
}
else if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
priorityOrderedPostProcessors.add(beanFactory.getBean(ppName, BeanFactoryPostProcessor.class));
}
else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
orderedPostProcessorNames.add(ppName);
}
else {
nonOrderedPostProcessorNames.add(ppName);
}
}
//按照优先级进行排序
sortPostProcessors(beanFactory, priorityOrderedPostProcessors);
//执行postProcessBeanFactory方法
invokeBeanFactoryPostProcessors(priorityOrderedPostProcessors, beanFactory);
//3.2存储实现了Ordered接口的类
List<BeanFactoryPostProcessor> orderedPostProcessors = new ArrayList<BeanFactoryPostProcessor>();
for (String postProcessorName : orderedPostProcessorNames) {
orderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));
}
//按照order排序
sortPostProcessors(beanFactory, orderedPostProcessors);
//执行postProcessBeanFactory方法
invokeBeanFactoryPostProcessors(orderedPostProcessors, beanFactory);
//3.3无序,直接调用
List<BeanFactoryPostProcessor> nonOrderedPostProcessors = new ArrayList<BeanFactoryPostProcessor>();
for (String postProcessorName : nonOrderedPostProcessorNames) {
nonOrderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));
}
//执行postProcessBeanFactory方法
invokeBeanFactoryPostProcessors(nonOrderedPostProcessors, beanFactory);
beanFactory.clearMetadataCache();
}
逻辑分析:
BeanFactoryPostProcessor和BeanDefinitionRegistryPostProcessor的区别:
- BeanFactoryPostProcessor: beanFactory的后置处理器; 在BeanFactory标准初始化之后调用, 来定制和修改beanFactory的内容; 所有的bean定义已保存加载beanFactory，但是bean的实例还未创建;
- BeanDefinitionRegistryPostProcessor: BeanDefinitionRegistryPostProcessor 继承于BeanFactoryPostProcessor; 在所有bean定义信息将要被加载, bean实例还未创建的时加载;优先于BeanFactoryPostProcessor执行;BeanDefinitionRegistryPostProcessor给容器中再额外添加一些组件;
- BeanDefinitionRegistryPostProcessor类型的BeanFactoryPostProcessor需要先激活postProcessBeanDefinitionRegistry方法, 然后再执行postProcessBeanFactory方法,而
BeanFactoryPostProcessor只需要执行 postProcessBeanFactory方法即可
注意: 对于BeanFactoryPostProcessor的处理主要分两种情况进行, 一个是对于BeanDefinitionRegistraryPostProcessor类的特殊处理, 一个是对普通的BeanFactoryPostProcessor进行处理; 而对于每种情况都需要考虑硬编码注入注册的后处理器和通过配置注入的后处理器;BeanDefinitionRegistryPostProcessor继承自BeanFactoryPostProcessor, 不但有BeanFactoryPostProcessor的特性, 同时还有自己定义的个性化方法, 也需要在此调用; 所以这里需要从beanFactoryPostProcessors中挑出BeanDefinitionRegistryPostProcessor的后处理器, 并进行其postProcessBeanDefinitionRegistry方法的激活
(1)创建registryPostProcessors和regularPostProcessors用于存储不同的后处理器
- registryPostProcessors: 记录通过 硬编码方式 和 配置注入方式 注册的BeanDefinitionRegistryPostProcessor类型的处理器
- regularPostProcessors: 记录通过硬编码方法注册的BeanFactoryPostProcessor类型的后处理器
(2) 对于硬编码注册的后处理器的处理; 遍历获取到的硬编码的后处理器,对两种类型的后处理器采取不同的处理方法:
- 如果是BeanDefinitionRegistryPostProcessor类型的则先执行postProcessBean
DefinitionRegistry()方法,将后处理器实例添加到registryPostProcessors集合中 - 如果是BeanFactoryPostProcessor类型的则添加到regularPostProcessors集合中即可
(3) 获取所有BeanDefinitionRegistryPostProcessor类型的处理器,根据实现priorityOrdered
或Ordered接口进行排序,并添加到registryPostProcessors集合中, 然后先执行postProcessBeanDefinitionRegistry方法
(4) 执行registryPostProcessors集合中和regularPostProcessors中存储的不同类型的后处理器的postProcessBeanFactory方法
(5) 对于普通beanFactory(未实现BeanDefinitionRegistry接口的BeanFactory类)的处理
BeanDefinitionRegistryPostProcessor后处理器只对实现BeanDefinitionRegistry接口的
ConfigurableListableBeanFactory有效, 所以如果判断所示的beanFactory并不是上述类型的就可以忽略BeanDefinitionRegistryPostProcessor, 直接处理BeanFactoryPostProcessor
(6)获取所有配置文件注入的BeanFactoryPostProcessor类型的后处理器根据实现priorityOrdered或Ordered接口按一定顺序执行postProcessBeanFactory方法
1.6.2 注册BeanPostProcessor
BeanPostProcessor是什么? 有什么作用?
(1) BeanPostProcessor接口有两个回调方法。当一个BeanPostProcessor的实现类注册到Spring IOC容器后，对于该Spring IOC容器所创建的每个bean实例在初始化方法（如afterPropertiesSet和任意已声明的init方法）调用前，将会调用BeanPostProcessor中的postProcessBeforeInitialization方法，而在bean实例初始化方法调用完成后，则会调用BeanPostProcessor中的postProcessAfterInitialization方法
整个调用顺序可以简单示意如下：
- Spring IOC容器实例化Bean
- 调用BeanPostProcessor的postProcessBeforeInitialization方法
- 调用bean实例的初始化方法
- 调用BeanPostProcessor的postProcessAfterInitialization方法
(2) 用户可以通过继承BeanPostProcessor接口, 重写postProcessBeforeInitialization和postProcessAfterInitialization方法对每一个bean进行修改,或者根据传入的beanName针对指定bean进行处理
可以看到，Spring容器通过BeanPostProcessor给了我们一个机会对Spring管理的bean进行再加工。比如：我们可以修改bean的属性，可以给bean生成一个动态代理实例等等。一些Spring AOP的底层处理也是通过实现BeanPostProcessor来执行代理包装逻辑的。
这里是对BeanPostProcessor进行注册, 真正的调用是在bean的实例化后,调用初始化方法前后执行的; 在BeanFactory中其实并没有实现后处理的自动注册, 所以调用的时候如果没有进行手动注册是不能使用的, 但是在ApplicationContext中添加了自动注册功能
registerBeanPostProcessors(beanFactory)
registerBeanPostProcessors方法的实现:
//public abstract class AbstractApplicationContext extends DefaultResourceLoader implements ConfigurableApplicationContext, DisposableBean
protected void registerBeanPostProcessors(ConfigurableListableBeanFactory beanFactory) {
PostProcessorRegistrationDelegate.registerBeanPostProcessors(beanFactory, this);
}
//class PostProcessorRegistrationDelegate
public static void registerBeanPostProcessors(ConfigurableListableBeanFactory beanFactory, AbstractApplicationContext applicationContext) {
String[] postProcessorNames = beanFactory.getBeanNamesForType(BeanPostProcessor.class, true, false);
/**
* BeanPostProcessorChecker是一个普通的信息打印,但是会出现一些请况:
* 当Spring的配置中的后处理器还没有被注册就已经开始了bean的初始化时,便会打印出BeanPostProcessorChecker中设定的信息
*/
int beanProcessorTargetCount = beanFactory.getBeanPostProcessorCount() + 1 + postProcessorNames.length;
beanFactory.addBeanPostProcessor(new BeanPostProcessorChecker(beanFactory, beanProcessorTargetCount));
//使用priorityOrdered保证顺序
List<BeanPostProcessor> priorityOrderedPostProcessors = new ArrayList<BeanPostProcessor>();
List<BeanPostProcessor> internalPostProcessors = new ArrayList<BeanPostProcessor>();
//使用Ordered保证顺序
List<String> orderedPostProcessorNames = new ArrayList<String>();
List<String> nonOrderedPostProcessorNames = new ArrayList<String>();
//将bean处理器分类存储
for (String ppName : postProcessorNames) {
if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
priorityOrderedPostProcessors.add(pp);
if (pp instanceof MergedBeanDefinitionPostProcessor) {
internalPostProcessors.add(pp);
}
}
else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
orderedPostProcessorNames.add(ppName);
}
else {
nonOrderedPostProcessorNames.add(ppName);
}
}
//第一步,注册所有实现了PriorityOrdered接口的BeanPostProcessors
sortPostProcessors(beanFactory, priorityOrderedPostProcessors);
registerBeanPostProcessors(beanFactory, priorityOrderedPostProcessors);
//第二步,注册所有实现Ordered的BeanPostProcessors
List<BeanPostProcessor> orderedPostProcessors = new ArrayList<BeanPostProcessor>();
for (String ppName : orderedPostProcessorNames) {
BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
orderedPostProcessors.add(pp);
if (pp instanceof MergedBeanDefinitionPostProcessor) {
internalPostProcessors.add(pp);
}
}
sortPostProcessors(beanFactory, orderedPostProcessors);
registerBeanPostProcessors(beanFactory, orderedPostProcessors);
//第三步,注册所有无序的BeanPostProcessor
List<BeanPostProcessor> nonOrderedPostProcessors = new ArrayList<BeanPostProcessor>();
for (String ppName : nonOrderedPostProcessorNames) {
BeanPostProcessor pp = beanFactory.getBean(ppName, BeanPostProcessor.class);
nonOrderedPostProcessors.add(pp);
if (pp instanceof MergedBeanDefinitionPostProcessor) {
internalPostProcessors.add(pp);
}
}
registerBeanPostProcessors(beanFactory, nonOrderedPostProcessors);
//第四步,注册所有MergedBeanDefinitionPostProcessors类型的BeanPostProcessor,并非重复注册
//在beanFactory.addBeanPostProcessor中会先移除已经存在的BeanPostProcessor
sortPostProcessors(beanFactory, internalPostProcessors);
registerBeanPostProcessors(beanFactory, internalPostProcessors);
//添加ApplicationListener探测器
beanFactory.addBeanPostProcessor(new ApplicationListenerDetector(applicationContext));
}
逻辑分析:
对于BeanFactoryPostProcessor的处理要区分两种情况, 一种方式是通过硬编码方式的处理, 另一种是通过配置文件方式的处理; 然而在BeanPostProcessor的处理中不需要考虑硬编码的方式; 对于BeanFactoryPostProcessor的处理, 不但要实现注册功能, 而且还要实现对后处理器的激活操作, 所以需要载入配置中的定义, 并进行激活; 对于BeanPostProcessor
的处理并不需要马上调用, 再说, 硬编码的方式实现的功能是将后处理器提取并调用, 这里并不需要调用, 不需要考虑硬编码的方式, 这里的功能只需要将配置文件BeanPostProcessor提取并注册进入benaFactory就可以了
1.6.3 初始化消息资源
protected void initMessageSource() {
ConfigurableListableBeanFactory beanFactory = getBeanFactory();
//如果在配置中已经配置了messageSource,那么将messageSource提取并记录在this.messageSource
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.isDebugEnabled()) {
logger.debug("Using MessageSource [" + this.messageSource + "]");
}
}
//如果用户并没有定义[配置文件,那么使用临时的DelegatingMessageSource以便于作为调用getMessage方法返回
else {
DelegatingMessageSource dms = new DelegatingMessageSource();
dms.setParentMessageSource(getInternalParentMessageSource());
this.messageSource = dms;
beanFactory.registerSingleton(MESSAGE_SOURCE_BEAN_NAME, this.messageSource);
if (logger.isDebugEnabled()) {
logger.debug("Unable to locate MessageSource with name '" + MESSAGE_SOURCE_BEAN_NAME +
"': using default [" + this.messageSource + "]");
}
}
}
逻辑分析:
啥也没有. . .
1.6.4初始化ApplicationEventMulticaster
spring的事件监听的简单用法(观察者模式):
(1) 定义监听事件
public class TestEvent extends ApplicationEvent{
public String msg;
public TestEvent(Object source){
super(source);
}
public TestEvent(Object source, String msg){
super(source);
this.msg=msg;
}
}
(2) 定义监听器
public class TestListener implement ApplicationListener{
public void onApplicationEvent(ApplicationEvent event){
TestEvent testEvent = (TestEvent)event;
testEvent.print();
}
}
(3) 添加配置文件
<bean id="testListener" class="com.test.event.TestEvent " />
(4)测试
public void testSimpleLoad(){
ApplicationContext bf= new ClassPathXmlApplicationContext("beanFactoryTest.xml");
TestEvent bean=new TestEvent ("hello","msg");
context.publishEvent(event);
}
initApplicationEventMulticaster的方式比较简单, 无非考虑两种情况
- 如果用户自定义了事件广播器, 那么使用用户自定义的事件广播器
- 如果用户没有自定义的事件广播器,那么使用默认的ApplicationEventMulticaster
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.isDebugEnabled()) {
logger.debug("Using ApplicationEventMulticaster [" + this.applicationEventMulticaster + "]");
}
}
//如果用户没有自定义事件广播器,那么使用默认的ApplicationEventMulticaster
else {
this.applicationEventMulticaster = new SimpleApplicationEventMulticaster(beanFactory);
beanFactory.registerSingleton(APPLICATION_EVENT_MULTICASTER_BEAN_NAME, this.applicationEventMulticaster);
if (logger.isDebugEnabled()) {
logger.debug("Unable to locate ApplicationEventMulticaster with name '" +
APPLICATION_EVENT_MULTICASTER_BEAN_NAME +
"': using default [" + this.applicationEventMulticaster + "]");
}
}
}
//public class SimpleApplicationEventMulticaster extends AbstractApplicationEventMulticaster
public void multicastEvent(final ApplicationEvent event, ResolvableType eventType) {
ResolvableType type = (eventType != null ? eventType : resolveDefaultEventType(event));
for (final ApplicationListener<?> listener : getApplicationListeners(event, type)) {
Executor executor = getTaskExecutor();
if (executor != null) {
executor.execute(new Runnable() {
@Override
public void run() {
invokeListener(listener, event);
}
});
}
else {
invokeListener(listener, event);
}
}
}
逻辑分析:
当产生Spring事件的时候会默认使用SimpleApplicationEventMulticaster类的multicastEvent
方法来广播事件, 遍历所有监听器, 并使用监听器中的onApplicationEvent方法来进行监听器的处理; 而对每个监听器来说, 其实都可以获取到产生的事件, 但是是否进行处理则有事件监听器来决定
1.6.5注册监听器
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);
}
}
}
1.7初始化非延迟加载单例
protected void finishBeanFactoryInitialization(ConfigurableListableBeanFactory beanFactory) {
// 初始化此上下文的转换服务
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));
}
String[] weaverAwareNames = beanFactory.getBeanNamesForType(LoadTimeWeaverAware.class, false, false);
for (String weaverAwareName : weaverAwareNames) {
getBean(weaverAwareName);
}
// Stop using the temporary ClassLoader for type matching.
beanFactory.setTempClassLoader(null);
//冻结所有bean定义,说明注册的bean定义将不被修改或任何进一步处理
beanFactory.freezeConfiguration();
//初始化剩下的非惰性的单实例(在加载配置文件时便提前实例化非懒加载的单例bean)
beanFactory.preInstantiateSingletons();
}
//public class DefaultListableBeanFactory extends AbstractAutowireCapableBeanFactory implements ConfigurableListableBeanFactory, BeanDefinitionRegistry, Serializable
public void preInstantiateSingletons() throws BeansException {
if (this.logger.isDebugEnabled()) {
this.logger.debug("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<String>(this.beanDefinitionNames);
// Trigger initialization of all non-lazy singleton beans...
for (String beanName : beanNames) {
//根据beanName]获取到bean的配置信息
RootBeanDefinition bd = getMergedLocalBeanDefinition(beanName);
//如果该bean不是抽象类,并且是单例,非延迟加载的,则进行实例化
if (!bd.isAbstract() && bd.isSingleton() && !bd.isLazyInit()) {
if (isFactoryBean(beanName)) {
final FactoryBean<?> factory = (FactoryBean<?>) getBean(FACTORY_BEAN_PREFIX + beanName);
boolean isEagerInit;
if (System.getSecurityManager() != null && factory instanceof SmartFactoryBean) {
isEagerInit = AccessController.doPrivileged(new PrivilegedAction<Boolean>() {
@Override
public Boolean run() {
return ((SmartFactoryBean<?>) factory).isEagerInit();
}
}, getAccessControlContext());
}
else {
isEagerInit = (factory instanceof SmartFactoryBean &&
((SmartFactoryBean<?>) factory).isEagerInit());
}
if (isEagerInit) {
getBean(beanName);
}
}
else {
getBean(beanName);
}
}
}
// Trigger post-initialization callback for all applicable beans...
for (String beanName : beanNames) {
Object singletonInstance = getSingleton(beanName);
if (singletonInstance instanceof SmartInitializingSingleton) {
final SmartInitializingSingleton smartSingleton = (SmartInitializingSingleton) singletonInstance;
if (System.getSecurityManager() != null) {
AccessController.doPrivileged(new PrivilegedAction<Object>() {
@Override
public Object run() {
smartSingleton.afterSingletonsInstantiated();
return null;
}
}, getAccessControlContext());
}
else {
smartSingleton.afterSingletonsInstantiated();
}
}
}
}
逻辑分析:
ApplicationContext实现的默认行为就是在启动时将所有单例bean提前进行实例化; 提前实例化意味着作为初始化的过程的一部分, ApplicationContext实例会创建并配置所有的单例bean
1.8 finishRefresh
在spring中还提供了Lifecycle接口, Lifecycle中包含start/stop方法, 实现此接口后Spring会保证在启动时调用start方法开始生命周期, 并在Spring关闭时调用stop方法来结束生命周期, 通常用来配置后台程序, 在启动后一直运行;
protected void finishRefresh() {
//为此上下文初始化生命周期处理器
initLifecycleProcessor();
//首先将刷新传播到生命周期处理器
getLifecycleProcessor().onRefresh();
//发布最终事件
publishEvent(new ContextRefreshedEvent(this));
// Participate in LiveBeansView MBean, if active.
LiveBeansView.registerApplicationContext(this);
}
1.8.1 initLifecycleProcessor
当ApplicationContext启动或停止时, 它会通过LifecycleProcessor来与所有声明的bean的周期做状态更新,而在LifecycleProcessor使用前需要初始化
protected void initLifecycleProcessor() {
ConfigurableListableBeanFactory beanFactory = getBeanFactory();
//如果存在自定义的LifecycleProcessor,则进行初始化
if (beanFactory.containsLocalBean(LIFECYCLE_PROCESSOR_BEAN_NAME)) {
this.lifecycleProcessor = beanFactory.getBean(LIFECYCLE_PROCESSOR_BEAN_NAME, LifecycleProcessor.class);
if (logger.isDebugEnabled()) {
logger.debug("Using LifecycleProcessor [" + this.lifecycleProcessor + "]");
}
}
//否则初始化默认LifecycleProcessor
else {
DefaultLifecycleProcessor defaultProcessor = new DefaultLifecycleProcessor();
defaultProcessor.setBeanFactory(beanFactory);
this.lifecycleProcessor = defaultProcessor;
beanFactory.registerSingleton(LIFECYCLE_PROCESSOR_BEAN_NAME, this.lifecycleProcessor);
if (logger.isDebugEnabled()) {
logger.debug("Unable to locate LifecycleProcessor with name '" +
LIFECYCLE_PROCESSOR_BEAN_NAME +
"': using default [" + this.lifecycleProcessor + "]");
}
}
}
1.8.2 onRefresh
启动所有实现了Lifecycle接口的bean
public void onRefresh() {
startBeans(true);
this.running = true;
}
private void startBeans(boolean autoStartupOnly) {
Map<String, Lifecycle> lifecycleBeans = getLifecycleBeans();
Map<Integer, LifecycleGroup> phases = new HashMap<Integer, LifecycleGroup>();
for (Map.Entry<String, ? extends Lifecycle> entry : lifecycleBeans.entrySet()) {
Lifecycle bean = entry.getValue();
if (!autoStartupOnly || (bean instanceof SmartLifecycle && ((SmartLifecycle) bean).isAutoStartup())) {
int phase = getPhase(bean);
LifecycleGroup group = phases.get(phase);
if (group == null) {
group = new LifecycleGroup(phase, this.timeoutPerShutdownPhase, lifecycleBeans, autoStartupOnly);
phases.put(phase, group);
}
group.add(entry.getKey(), bean);
}
}
if (phases.size() > 0) {
List<Integer> keys = new ArrayList<Integer>(phases.keySet());
Collections.sort(keys);
for (Integer key : keys) {
phases.get(key).start();
}
}
}
1.8.3 onRefresh
当完成ApplicationContext初始化的时候,要通过spring中的事件发布机制来发出ContextRefreshEvent事件, 以保证对应的监听器可以做进一步的逻辑处理
public void publishEvent(ApplicationEvent event) {
publishEvent(event, null);
}
protected void publishEvent(Object event, ResolvableType eventType) {
Assert.notNull(event, "Event must not be null");
if (logger.isTraceEnabled()) {
logger.trace("Publishing event in " + getDisplayName() + ": " + event);
}
// Decorate event as an ApplicationEvent if necessary
ApplicationEvent applicationEvent;
if (event instanceof ApplicationEvent) {
applicationEvent = (ApplicationEvent) event;
}
else {
applicationEvent = new PayloadApplicationEvent<Object>(this, event);
if (eventType == null) {
eventType = ResolvableType.forClassWithGenerics(PayloadApplicationEvent.class, event.getClass());
}
}
// Multicast right now if possible - or lazily once the multicaster is initialized
if (this.earlyApplicationEvents != null) {
this.earlyApplicationEvents.add(applicationEvent);
}
else {
getApplicationEventMulticaster().multicastEvent(applicationEvent, eventType);
}
// Publish event via parent context as well...
if (this.parent != null) {
if (this.parent instanceof AbstractApplicationContext) {
((AbstractApplicationContext) this.parent).publishEvent(event, eventType);
}
else {
this.parent.publishEvent(event);
}
}
}
扫一扫
2万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
