AnnotationConfigApplicationContext 注解版的ApplicationContext
DefaultListableBeanFactory 实例化工厂 这是一个非常重要要的方法
AnnotationBeanDefinitionReader 读取bean
AnnotationBeanDefinitionScanner 扫描配置类,一般不会使用到,主要传入了String 或者外部调用scan
GenericApplicationContext
register(componentClasses);
BeanDefinition
refresh()
// Instantiate all remaining (non-lazy-init) singletons.
finishBeanFactoryInitialization(beanFactory);
beanFactory.preInstantiateSingletons();
getBean(beanName);
// Create bean instance.
if (mbd.isSingleton()) {
//getSingleton中的第二个参数类型是ObjectFactory<?>,是一个函数式接口,不会立刻执行,而是在
sharedInstance = getSingleton(beanName, () -> {
try {
return createBean(beanName, mbd, args);
} catch (BeansException ex) {
// Explicitly remove instance from singleton cache: It might have been put there
// eagerly by the creation process, to allow for circular reference resolution.
// Also remove any beans that received a temporary reference to the bean.
destroySingleton(beanName);
throw ex;
}
});
bean = getObjectForBeanInstance(sharedInstance, name, beanName, mbd);
}
createBean(beanName, mbd, args);
1. InstantiationAwareBeanPostProcessor#postProcessBeforeInstantiation 解析AOP相关 , 这里可以拦截Bean,使用我们自己创建的Bean
2. SmartInstantiationAwareBeanPostProcessor#determineCandidateConstructors 选择构造器
---- 开始创建对象
3. autowireConstructor(beanName, mbd, ctors, null) or instantiateBean(beanName, mbd) 创建最原始的对象,没有任何属性的对象
4. MergedBeanDefinitionPostProcessor#postProcessMergedBeanDefinition 处理AutoWired value 预解析
5. 将原始的bean和beanDefinition 以及BeanName 放入三级缓存,用来解决循环依赖 addSingletonFactory(beanName, () -> getEarlyBeanReference(beanName, mbd, bean));
6. SmartInstantiationAwareBeanPostProcessor#getEarlyBeanReference 获得早期暴露对象
---- 开始属性赋值
7. InstantiationAwareBeanPostProcessor#postProcessAfterInstantiation 提供可以修改Bean状态的后置处理,可以支持属性注入的方式
8. PropertyValues 属性值确认
9. InstantiationAwareBeanPostProcessor#postProcessPropertyValues 可以修改属性的值
10. applyPropertyValues(beanName, mbd, bw, pvs); 开始真正的属性赋值
---- 初始化Bean
11. initializeBean
12. 调用Aware methods invok