1. DESC
Spring对beanFactory的处理
2. CODE
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();
}
}
}
3. 从上往下RUSH
3.1 prepareRefresh()
这里不用细看就是自身进行些配置和参数校验什么的
3.2 obtainFreshBeanFactory()
- 加载NameSpacehandler
- 使用各个NameSpcaceHandler生成Beandifinitions并注册到beanfactory里面去
3.2.1 加载NameSpaceHandler
NameSpaceHandler
加载过程的解析已经写过就不再写了; 参看前面的文章
3.2.2 NameSpaceHandler处理生成bean的定义(注意只是生成beanDefinition而不是生成具体的bean而且相关的Class文件也没有加载)
- NamespaceHandlerSupport
//返回也没用,应该定义为void的,parserContext的registry就是beanFactory
public BeanDefinition parse(Element element, ParserContext parserContext) {
//获取具体的BeanDefinitionParser,比如说ComponentScanBeanDefinitionParser
return findParserForElement(element, parserContext).parse(element, parserContext);
}
ComponentScanBeanDefinitionParser
这是个样板例子,一看就知道怎么回事
public BeanDefinition parse(Element element, ParserContext parserContext) {
String basePackage = element.getAttribute(BASE_PACKAGE_ATTRIBUTE);//获取basepackage设定的包名
basePackage = parserContext.getReaderContext().getEnvironment().resolvePlaceholders(basePackage);//有可能使用了$
String[] basePackages = StringUtils.tokenizeToStringArray(basePackage,ConfigurableApplicationContext.CONFIG_LOCATION_DELIMITERS);//解析出全部的package
// Actually scan for bean definitions and register them.
ClassPathBeanDefinitionScanner scanner = configureScanner(parserContext, element);//配置扫描器
Set<BeanDefinitionHolder> beanDefinitions = scanner.doScan(basePackages);//扫包
registerComponents(parserContext.getReaderContext(), beanDefinitions, element);//向beanFactory注册
return null;
}
3.3 prepareBeanFactory(beanFactory)
主要是完成BeanFactoryPostProcessors的初始化
protected void prepareBeanFactory(ConfigurableListableBeanFactory beanFactory) {
...
//注意这是LTW,加载时代码织入进行增强AOP
if (beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
}
...
}
3.4 invokeBeanFactoryPostProcessors(beanFactory) 执行BeanFactoryPostProcessors,
对BeanFactory启动处理流程
protected void invokeBeanFactoryPostProcessors(ConfigurableListableBeanFactory beanFactory) {
PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(beanFactory, getBeanFactoryPostProcessors()); //需要注意的有个AspectJWeavingEnabler比较特殊,这个类的目的在于启用ClassLoader级别的Aop,和以前的Instrument In Jvm 有点类似,
// 检测是否有LTW支持,
if (beanFactory.getTempClassLoader() == null && beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
}
}
3.5 后面的几个方法感觉不用写了
就是bean的初始化什么的了;
其实想抓下Transactional的实现代码的;(这个有点不太明白和JVM redifineClass是怎么对活动栈帧进行方法栈的替换)
但我对AspectJ实在不熟,先放弃吧.等我点了ApsectJ的科技树再回来补充;
4. 总结整体流程
ContextLoaderListener 初始化
new DefaultListableBeanFactory() 创建beanFactroy
new XmlBeanDefinitionReader(beanFactory) 创建解析器
new BeanDefinitionDocumentReader
加载配置文件applicationContext.xml
根据 配置文件内的tag的namespace 及 lib下所有jar的/META-INF/spring.handlers 确定NamespaceHandler 并对其初始化
根据 tag的具体值确定BeanDefinitionParser();调用parser.parse(Element element, ParserContext parserContext) 完成BeanDefinition的注册,parserContext的registry 就是最开始创建的beanFactory;
postProcessBeanFactory()完成各种beanFatoryPostProcessor的初始化
执行这些完成各种beanFatoryPostProcessor 注意里面有个比较特殊属的AspectJWeavingEnabler 是负责启用ClassLoader级别Aop的核心逻辑(就是在ClassLoader上注入ClassFileTransformer)
后面就是bean的各种加载逻辑了...不写了