注：本文源码基于Spring-5.2.2.RELEASE版本
ConfigurationClassPostProcessor 功能概述
ConfigurationClassPostProcessor 是spring框架中提供解析配置类的一个及其重要的后置处理器，其作用是解析被@Configuration注解的类（ConfigurationClassUtils#checkConfigurationClassCandidate这个方法判断），这个注解是一个类能被该后置处理器解析的必要条件；如果这些类还有如下这些注解，也会被依次解析：
- @Component
- @PropertySources
- @ComponentScan、@ComponentScans注解的类
- @Import注解的类
- @ImportResource
- @Bean注解方法
但注册bean的顺序会跟解析的顺序不太一样（有的会先缓存我把这个问题称为bean等级的问题 哈哈），后面文章会讲到
其原理是以 提供的配置类为入口，递归解析其类里包含的所有以上注解；
- 其实现了BeanDefinitionRegistryPostProcessor和BeanFactoryPostProcessor：
在容器BeanFactory创建好并加载了优先级最高的beanDefinition后（正常流程来说，配置文件里配置的bean优先级最高），会执行 postProcessBeanDefinitionRegistry 方法(先)和 postProcessBeanFactory 方法(后）；
ConfigurationClassPostProcessor#processConfigBeanDefinitions
- postProcessBeanDefinitionRegistry 方法里解析BeanDefinition逻辑主要是processConfigBeanDefinitions方法完成的
方法签名：org.springframework.context.annotation.ConfigurationClassPostProcessor#processConfigBeanDefinitions
下面方法只保留了核心方法
public void processConfigBeanDefinitions(BeanDefinitionRegistry registry) {
List<BeanDefinitionHolder> configCandidates = new ArrayList<>();
String[] candidateNames = registry.getBeanDefinitionNames();
... 省略部分代码...
// 初始化解析器
// Parse each @Configuration class
ConfigurationClassParser parser = new ConfigurationClassParser(
this.metadataReaderFactory, this.problemReporter, this.environment,
this.resourceLoader, this.componentScanBeanNameGenerator, registry);
Set<BeanDefinitionHolder> candidates = new LinkedHashSet<>(configCandidates);
Set<ConfigurationClass> alreadyParsed = new HashSet<>(configCandidates.size());
do {
//@A
parser.parse(candidates);
parser.validate();
Set<ConfigurationClass> configClasses = new LinkedHashSet<>(parser.getConfigurationClasses());
configClasses.removeAll(alreadyParsed);
// Read the model and create bean definitions based on its content
if (this.reader == null) {
this.reader = new ConfigurationClassBeanDefinitionReader(
registry, this.sourceExtractor, this.resourceLoader, this.environment,
this.importBeanNameGenerator, parser.getImportRegistry());
}
//@B
this.reader.loadBeanDefinitions(configClasses);
alreadyParsed.addAll(configClasses);
candidates.clear();
if (registry.getBeanDefinitionCount() > candidateNames.length) {
String[] newCandidateNames = registry.getBeanDefinitionNames();
Set<String> oldCandidateNames = new HashSet<>(Arrays.asList(candidateNames));
Set<String> alreadyParsedClasses = new HashSet<>();
for (ConfigurationClass configurationClass : alreadyParsed) {
alreadyParsedClasses.add(configurationClass.getMetadata().getClassName());
}
for (String candidateName : newCandidateNames) {
if (!oldCandidateNames.contains(candidateName)) {
BeanDefinition bd = registry.getBeanDefinition(candidateName);
if (ConfigurationClassUtils.checkConfigurationClassCandidate(bd, this.metadataReaderFactory) &&
!alreadyParsedClasses.contains(bd.getBeanClassName())) {
candidates.add(new BeanDefinitionHolder(bd, candidateName));
}
}
}
candidateNames = newCandidateNames;
}
}
while (!candidates.isEmpty());
... 省略部分代码...
}
@A：其主要逻辑是委托ConfigurationClassParser类来完成@Configuration类解析
@B：将ConfigurationClassParser扩展扫描到的类（注意这里是发现的所有类），类注册到beandefinition
ConfigurationClassParser#parse
以下是配置类【Configuration标记的类】流程控制核心方法：
org.springframework.context.annotation.ConfigurationClassParser#parse(java.util.Set<org.springframework.beans.factory.config.BeanDefinitionHolder>)
parse 方法不会进行beandefiniton的注册，只是通过扫描将beandefinition存入自己的configurationClasses属性，真正注册是在上面的@B处方法；
public void parse(Set<BeanDefinitionHolder> configCandidates) {
for (BeanDefinitionHolder holder : configCandidates) {
BeanDefinition bd = holder.getBeanDefinition();
try {
if (bd instanceof AnnotatedBeanDefinition) {
//@A
parse(((AnnotatedBeanDefinition) bd).getMetadata(), holder.getBeanName());
}
else if (bd instanceof AbstractBeanDefinition && ((AbstractBeanDefinition) bd).hasBeanClass()) {
//@B
parse(((AbstractBeanDefinition) bd).getBeanClass(), holder.getBeanName());
}
else {
//@C
parse(bd.getBeanClassName(), holder.getBeanName());
}
}
catch (BeanDefinitionStoreException ex) {
throw ex;
}
catch (Throwable ex) {
throw new BeanDefinitionStoreException(
"Failed to parse configuration class [" + bd.getBeanClassName() + "]", ex);
}
}
//@D
this.deferredImportSelectorHandler.process();
}
//@A、@B、@C：方法内都是将目标类封装成一个ConfigurationClass对象，调用processConfigurationClass方法解析配置配类
//@D：延时处理被@Import引入的DeferredImportSelector接口的子类。在@A、@B、@C方法中只会缓存被@Import引入的 DeferredImportSelector子类，不会做具体解析；spring boot中的AutoConfigurationImportSelector就是一个DeferredImportSelector子类；
DeferredImportSelector 的设计目的是在所有其他的配置类被处理后才处理。
上面parse 方法会调用 processConfigurationClass 方法
protected void processConfigurationClass(ConfigurationClass configClass) throws IOException {
if (this.conditionEvaluator.shouldSkip(configClass.getMetadata(), ConfigurationPhase.PARSE_CONFIGURATION)) {
return;
}
ConfigurationClass existingClass = this.configurationClasses.get(configClass);
if (existingClass != null) {
if (configClass.isImported()) {
if (existingClass.isImported()) {
existingClass.mergeImportedBy(configClass);
}
// Otherwise ignore new imported config class; existing non-imported class overrides it.
return;
}
else {
// Explicit bean definition found, probably replacing an import.
// Let's remove the old one and go with the new one.
this.configurationClasses.remove(configClass);
this.knownSuperclasses.values().removeIf(configClass::equals);
}
}
// Recursively process the configuration class and its superclass hierarchy.
SourceClass sourceClass = asSourceClass(configClass);
do {
// @A
sourceClass = doProcessConfigurationClass(configClass, sourceClass);
}
while (sourceClass != null);
// @B
this.configurationClasses.put(configClass, configClass);
}
@A：doProcessConfigurationClass主要是解析配置类，如果配置类还有父类（不是以java开头的包）则返回值sourceClass就不会为空，则继续循环直到没有父类可以解析；
@B：将当前的的ConfigurationClass缓存入configurationClasses属性，注意这里的configurationClasses是ConfigurationClassParser的属性；类型是一个HashMap，为什么是设计成一个HashMap呢，是为了后面递归地往里面放对象
ConfigurationClassParser#doProcessConfigurationClass
1、该方法主要解析配置类里的 @Component，@PropertySources，@ComponentScans, @ComponentScan，@Import，@ImportResource 注解的类 和 @Bean 注解的 method；
2、其中如果被@ComponentScans, @ComponentScan扫描到有被@Configuration注解的类，则调用parse方法形成递归；
方法内容简要注释如下：
protected final SourceClass doProcessConfigurationClass(ConfigurationClass configClass, SourceClass sourceClass)
throws IOException {
// 1、如果该类有@Component注解，则解析内部嵌套的类（如果有）
if (configClass.getMetadata().isAnnotated(Component.class.getName())) {
// Recursively process any member (nested) classes first
processMemberClasses(configClass, sourceClass);
}
// 2、如果目标类有@PropertySource注解，则解析其对应的字段
// Process any @PropertySource annotations
for (AnnotationAttributes propertySource : AnnotationConfigUtils.attributesForRepeatable(
sourceClass.getMetadata(), PropertySources.class,
org.springframework.context.annotation.PropertySource.class)) {
if (this.environment instanceof ConfigurableEnvironment) {
processPropertySource(propertySource);
}
else {
logger.info("Ignoring @PropertySource annotation on [" + sourceClass.getMetadata().getClassName() +
"]. Reason: Environment must implement ConfigurableEnvironment");
}
}
// 3、解析@ComponentScans和@ComponentScan注解；扫描到待解析的目标类后，调用 parse方法对目标类进行进一步解析，调用parser方法会将目标类放入 configurationClasses 属性
// Process any @ComponentScan annotations
Set<AnnotationAttributes> componentScans = AnnotationConfigUtils.attributesForRepeatable(
sourceClass.getMetadata(), ComponentScans.class, ComponentScan.class);
if (!componentScans.isEmpty() &&
!this.conditionEvaluator.shouldSkip(sourceClass.getMetadata(), ConfigurationPhase.REGISTER_BEAN)) {
for (AnnotationAttributes componentScan : componentScans) {
// The config class is annotated with @ComponentScan -> perform the scan immediately
// 注意：这里会将扫描到的类注册到容器beanDefinition，和@Import引入的类注册时机不一样，后者会在外层调用方最后注册到容器
Set<BeanDefinitionHolder> scannedBeanDefinitions =
this.componentScanParser.parse(componentScan, sourceClass.getMetadata().getClassName());
// Check the set of scanned definitions for any further config classes and parse recursively if needed
for (BeanDefinitionHolder holder : scannedBeanDefinitions) {
BeanDefinition bdCand = holder.getBeanDefinition().getOriginatingBeanDefinition();
if (bdCand == null) {
bdCand = holder.getBeanDefinition();
}
if (ConfigurationClassUtils.checkConfigurationClassCandidate(bdCand, this.metadataReaderFactory)) {
// 调用 parse 方法，形成递归
parse(bdCand.getBeanClassName(), holder.getBeanName());
}
}
}
}
// 4、处理@Import注解，会处理多种类型的类；下面单独分析该方法
// Process any @Import annotations
processImports(configClass, sourceClass, getImports(sourceClass), true);
// 5、处理@ImportResource注解，被引入的类会被缓存到当前的configClass的importedResources属性中
// Process any @ImportResource annotations
AnnotationAttributes importResource =
AnnotationConfigUtils.attributesFor(sourceClass.getMetadata(), ImportResource.class);
if (importResource != null) {
String[] resources = importResource.getStringArray("locations");
Class<? extends BeanDefinitionReader> readerClass = importResource.getClass("reader");
for (String resource : resources) {
String resolvedResource = this.environment.resolveRequiredPlaceholders(resource);
configClass.addImportedResource(resolvedResource, readerClass);
}
}
// 6、解析@Bean注解的方法
// Process individual @Bean methods
Set<MethodMetadata> beanMethods = retrieveBeanMethodMetadata(sourceClass);
for (MethodMetadata methodMetadata : beanMethods) {
// 将扫描到的注解方法缓存进当前configClass的beanMethods的Set集合属性中
configClass.addBeanMethod(new BeanMethod(methodMetadata, configClass));
}
// Process default methods on interfaces
processInterfaces(configClass, sourceClass);
// 7、如果有父类，则返回父类信息，调用方判断返回值不是空会继续解析父类
// Process superclass, if any
if (sourceClass.getMetadata().hasSuperClass()) {
String superclass = sourceClass.getMetadata().getSuperClassName();
if (superclass != null && !superclass.startsWith("java") &&
!this.knownSuperclasses.containsKey(superclass)) {
this.knownSuperclasses.put(superclass, configClass);
// Superclass found, return its annotation metadata and recurse
return sourceClass.getSuperClass();
}
}
// No superclass -> processing is complete
return null;
}
ConfigurationClassParser#processImports
该方法处理 @Import注解
private void processImports(ConfigurationClass configClass, SourceClass currentSourceClass, Collection<SourceClass> importCandidates, boolean checkForCircularImports) {
if (importCandidates.isEmpty()) {
return;
}
//1、 检测报告循环依赖
if (checkForCircularImports && isChainedImportOnStack(configClass)) {
this.problemReporter.error(new CircularImportProblem(configClass, this.importStack));
} else {
this.importStack.push(configClass);
try {
for (SourceClass candidate : importCandidates) {
//2、 如果被Import的是ImportSelector实现类，
if (candidate.isAssignable(ImportSelector.class)) {
// Candidate class is an ImportSelector -> delegate to it to determine imports
Class<?> candidateClass = candidate.loadClass();
ImportSelector selector = ParserStrategyUtils.instantiateClass(candidateClass, ImportSelector.class,
this.environment, this.resourceLoader, this.registry);
//2.1、 如果是DeferredImportSelector的子类，则会被放入到 deferredImportSelectors 这个集合中待延迟处理；springboot的AutoConfigurationImportSelector.class就是这样的一种类
if (selector instanceof DeferredImportSelector) {
this.deferredImportSelectorHandler.handle(configClass, (DeferredImportSelector) selector);
}
else {
//2.2、 否则递归调用 processImports 方法，继续解析被@Import到的类，最终效果是将引入的类缓存进ConfigurationClassParser#configurationClasses属性中
String[] importClassNames = selector.selectImports(currentSourceClass.getMetadata());
Collection<SourceClass> importSourceClasses = asSourceClasses(importClassNames);
processImports(configClass, currentSourceClass, importSourceClasses, false);
}
}
//3、 如果被引入的类是 ImportBeanDefinitionRegistrar子类，则会缓存到configClass对象的importBeanDefinitionRegistrars属性中；
// 在最外层的调用方ConfigurationClassBeanDefinitionReader#loadBeanDefinitionsForConfigurationClass方法里统一进行注册
else if (candidate.isAssignable(ImportBeanDefinitionRegistrar.class)) {
// Candidate class is an ImportBeanDefinitionRegistrar ->
// delegate to it to register additional bean definitions
Class<?> candidateClass = candidate.loadClass();
ImportBeanDefinitionRegistrar registrar =
ParserStrategyUtils.instantiateClass(candidateClass, ImportBeanDefinitionRegistrar.class,
this.environment, this.resourceLoader, this.registry);
configClass.addImportBeanDefinitionRegistrar(registrar, currentSourceClass.getMetadata());
}
//4、其他场景，比如直接@Import的一个类或者是通过2.2分支递归进入该方法，则调用processConfigurationClass方法形成递归，将解析到的类缓存进configurationClasses属性中
else {
// Candidate class not an ImportSelector or ImportBeanDefinitionRegistrar ->
// process it as an @Configuration class
this.importStack.registerImport(
currentSourceClass.getMetadata(), candidate.getMetadata().getClassName());
processConfigurationClass(candidate.asConfigClass(configClass));
}
}
}
catch (BeanDefinitionStoreException ex) {
throw ex;
}
catch (Throwable ex) {
throw new BeanDefinitionStoreException(
"Failed to process import candidates for configuration class [" +
configClass.getMetadata().getClassName() + "]", ex);
}
finally {
this.importStack.pop();
}
}
}
ConfigurationClassParser#retrieveBeanMethodMetadata
回到doProcessConfigurationClass方法中调用的retrieveBeanMethodMetadata方法，该方法是扫描当前目标类里被@Bean标记的方法，封装成MethodMetadata集合返回
private Set<MethodMetadata> retrieveBeanMethodMetadata(SourceClass sourceClass) {
AnnotationMetadata original = sourceClass.getMetadata();
//@A 获得@Bean标记的方法
Set<MethodMetadata> beanMethods = original.getAnnotatedMethods(Bean.class.getName());
if (beanMethods.size() > 1 && original instanceof StandardAnnotationMetadata) {
// Try reading the class file via ASM for deterministic declaration order...
// Unfortunately, the JVM's standard reflection returns methods in arbitrary
// order, even between different runs of the same application on the same JVM.
try {
AnnotationMetadata asm =
this.metadataReaderFactory.getMetadataReader(original.getClassName()).getAnnotationMetadata();
Set<MethodMetadata> asmMethods = asm.getAnnotatedMethods(Bean.class.getName());
if (asmMethods.size() >= beanMethods.size()) {
Set<MethodMetadata> selectedMethods = new LinkedHashSet<>(asmMethods.size());
for (MethodMetadata asmMethod : asmMethods) {
for (MethodMetadata beanMethod : beanMethods) {
if (beanMethod.getMethodName().equals(asmMethod.getMethodName())) {
selectedMethods.add(beanMethod);
break;
}
}
}
if (selectedMethods.size() == beanMethods.size()) {
// All reflection-detected methods found in ASM method set -> proceed
beanMethods = selectedMethods;
}
}
}
catch (IOException ex) {
logger.debug("Failed to read class file via ASM for determining @Bean method order", ex);
// No worries, let's continue with the reflection metadata we started with...
}
}
return beanMethods;
}
方法再跳回到 ConfigurationClassPostProcessor#processConfigBeanDefinitions
ConfigurationClassBeanDefinitionReader#loadBeanDefinitions
该方法是将 ConfigurationClassParser 扫描到的configurationClasses集合进行beanDefinition进行注册，内部实现是通过循环调用loadBeanDefinitionsForConfigurationClass方法
ConfigurationClassBeanDefinitionReader#loadBeanDefinitionsForConfigurationClass
该方法实际上是将通过@Import、@Bean等注解方式注册的类解析成BeanDefinition，然后注册到BeanDefinitionMap中。
这个方法决定了beanDefinition的注册顺序，也就产生了不同方式注册bean的“等级”关系，因为beanDefinition注册会被缓存到DefaultListableBeanFactory#beanDefinitionNames这个ArrayList集合中，初始实例化先后也是按照这个顺序来的（也就是说注册顺序影响到实例化顺序，非互相依赖的情况下）
private void loadBeanDefinitionsForConfigurationClass(ConfigurationClass configClass, TrackedConditionEvaluator trackedConditionEvaluator) {
if (trackedConditionEvaluator.shouldSkip(configClass)) {
String beanName = configClass.getBeanName();
if (StringUtils.hasLength(beanName) && this.registry.containsBeanDefinition(beanName)) {
this.registry.removeBeanDefinition(beanName);
}
this.importRegistry.removeImportingClass(configClass.getMetadata().getClassName());
return;
}
if (configClass.isImported()) {
registerBeanDefinitionForImportedConfigurationClass(configClass);
}
for (BeanMethod beanMethod : configClass.getBeanMethods()) {
loadBeanDefinitionsForBeanMethod(beanMethod);
}
// 判断当前的bean中是否含有@Bean注解的方法，如果有，需要把这些方法产生的bean放入到BeanDefinitionMap当中
loadBeanDefinitionsFromImportedResources(configClass.getImportedResources());
// 如果bean上存在@Import注解，且import的是一个实现了ImportBeanDefinitionRegistrar接口,则执行ImportBeanDefinitionRegistrar的registerBeanDefinitions()方法
loadBeanDefinitionsFromRegistrars(configClass.getImportBeanDefinitionRegistrars());
}
整个beanDefinition注册流程还是比较复杂的，也是非常核心的方法；学spring，这个方法的源码我想还是必须要看明白的！
2482
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
