ConfigurationClassPostProcessor工作機制-概覽

1.AbstractApplicationContext#refresh

invokeBeanFactoryPostProcessors(beanFactory);

2.AbstractApplicationContext#invokeBeanFactoryPostProcessors

    protected void invokeBeanFactoryPostProcessors(ConfigurableListableBeanFactory beanFactory) {
        // GO
        PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(beanFactory, getBeanFactoryPostProcessors());

        // Detect a LoadTimeWeaver and prepare for weaving, if found in the meantime
        // (e.g. through an @Bean method registered by ConfigurationClassPostProcessor)
        if (!IN_NATIVE_IMAGE && beanFactory.getTempClassLoader() == null && beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
            beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
            beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
        }
    }

3.PostProcessorRegistrationDelegate#invokeBeanFactoryPostProcessors

invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry, beanFactory.getApplicationStartup());

4.PostProcessorRegistrationDelegate#invokeBeanDefinitionRegistryPostProcessors

    private static void invokeBeanDefinitionRegistryPostProcessors(
            Collection<? extends BeanDefinitionRegistryPostProcessor> postProcessors, BeanDefinitionRegistry registry, ApplicationStartup applicationStartup) {

        for (BeanDefinitionRegistryPostProcessor postProcessor : postProcessors) {
            StartupStep postProcessBeanDefRegistry = applicationStartup.start("spring.context.beandef-registry.post-process")
                    .tag("postProcessor", postProcessor::toString);
            postProcessor.postProcessBeanDefinitionRegistry(registry);
            postProcessBeanDefRegistry.end();
        }
    }

5.ConfigurationClassPostProcessor#postProcessBeanDefinitionRegistry

    @Override
    public void postProcessBeanDefinitionRegistry(BeanDefinitionRegistry registry) {
        int registryId = System.identityHashCode(registry);
        if (this.registriesPostProcessed.contains(registryId)) {
            throw new IllegalStateException(
                    "postProcessBeanDefinitionRegistry already called on this post-processor against " + registry);
        }
        if (this.factoriesPostProcessed.contains(registryId)) {
            throw new IllegalStateException(
                    "postProcessBeanFactory already called on this post-processor against " + registry);
        }
        this.registriesPostProcessed.add(registryId);

        processConfigBeanDefinitions(registry);
    }

6.ConfigurationClassPostProcessor#processConfigBeanDefinitions

    public void processConfigBeanDefinitions(BeanDefinitionRegistry registry) {
        List<BeanDefinitionHolder> configCandidates = new ArrayList<>();
        String[] candidateNames = registry.getBeanDefinitionNames();

        for (String beanName : candidateNames) {
            BeanDefinition beanDef = registry.getBeanDefinition(beanName);
            if (beanDef.getAttribute(ConfigurationClassUtils.CONFIGURATION_CLASS_ATTRIBUTE) != null) {
                if (logger.isDebugEnabled()) {
                    logger.debug("Bean definition has already been processed as a configuration class: " + beanDef);
                }
            }
            // checkConfigurationClassCandidate()會判斷一個是否是一個配置類,并為BeanDefinition設(shè)置屬性為lite或者full隔心。
            // 在這兒為BeanDefinition設(shè)置lite和full屬性值是為了后面在使用
            // 如果加了@Configuration分瘦,那么對應(yīng)的BeanDefinition為full;
            // 如果加了@Bean,@Component,@ComponentScan,@Import,@ImportResource這些注解濒持,則為lite。
            // lite和full均表示這個BeanDefinition對應(yīng)的類是一個配置類
            else if (ConfigurationClassUtils.checkConfigurationClassCandidate(beanDef, this.metadataReaderFactory)) {
                configCandidates.add(new BeanDefinitionHolder(beanDef, beanName));
            }
        }

        // Return immediately if no @Configuration classes were found
        if (configCandidates.isEmpty()) {
            return;
        }

        // Sort by previously determined @Order value, if applicable
        configCandidates.sort((bd1, bd2) -> {
            int i1 = ConfigurationClassUtils.getOrder(bd1.getBeanDefinition());
            int i2 = ConfigurationClassUtils.getOrder(bd2.getBeanDefinition());
            return Integer.compare(i1, i2);
        });

        // Detect any custom bean name generation strategy supplied through the enclosing application context
        SingletonBeanRegistry sbr = null;
        if (registry instanceof SingletonBeanRegistry) {
            sbr = (SingletonBeanRegistry) registry;
            if (!this.localBeanNameGeneratorSet) {
                // beanName的生成器词身,因為后面會掃描出所有加入到spring容器中calss類胧谈,然后把這些class
                // 解析成BeanDefinition類培遵,此時需要利用BeanNameGenerator為這些BeanDefinition生成beanName
                BeanNameGenerator generator = (BeanNameGenerator) sbr.getSingleton(
                        AnnotationConfigUtils.CONFIGURATION_BEAN_NAME_GENERATOR);
                if (generator != null) {
                    this.componentScanBeanNameGenerator = generator;
                    this.importBeanNameGenerator = generator;
                }
            }
        }

        if (this.environment == null) {
            this.environment = new StandardEnvironment();
        }

        // Parse each @Configuration class
        // 解析所有加了@Configuration注解的類
        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 {
            StartupStep processConfig = this.applicationStartup.start("spring.context.config-classes.parse");
            // 解析配置類挪丢,在此處會解析配置類上的注解(ComponentScan掃描出的類狈谊,@Import注冊的類喜命,以及@Bean方法定義的類)
            // 注意:這一步只會將加了@Configuration注解以及通過@ComponentScan注解掃描的類才會加入到BeanDefinitionMap中
            // 通過其他注解(例如@Import、@Bean)的方式河劝,在parse()方法這一步并不會將其解析為BeanDefinition放入到BeanDefinitionMap中壁榕,
            // 而是先解析成ConfigurationClass類
            // 真正放入到map中是在下面的this.reader.loadBeanDefinitions()方法中實現(xiàn)的
            // GO
            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());
            }
            // 將上一步parser解析出的ConfigurationClass類加載成BeanDefinition
            // 實際上經(jīng)過上一步的parse()后,解析出來的bean已經(jīng)放入到BeanDefinition中了赎瞎,但是由于這些bean可能會引入新的bean牌里,
            // 例如實現(xiàn)了ImportBeanDefinitionRegistrar或者ImportSelector接口的bean,或者bean中存在被@Bean注解的方法
            // 因此需要執(zhí)行一次loadBeanDefinition()务甥,這樣就會執(zhí)行ImportBeanDefinitionRegistrar或者ImportSelector接口的方法
            // 或者@Bean注釋的方法
            // GO
            this.reader.loadBeanDefinitions(configClasses);
            alreadyParsed.addAll(configClasses);
            processConfig.tag("classCount", () -> String.valueOf(configClasses.size())).end();

            candidates.clear();
            // 這里判斷registry.getBeanDefinitionCount() > candidateNames.length的目的是為了知道
            // reader.loadBeanDefinitions(configClasses)這一步有沒有向BeanDefinitionMap中添加新的BeanDefinition
            // 實際上就是看配置類(例如AppConfig類會向BeanDefinitionMap中添加bean)
            // 如果有牡辽,registry.getBeanDefinitionCount()就會大于candidateNames.length
            // 這樣就需要再次遍歷新加入的BeanDefinition,并判斷這些bean是否已經(jīng)被解析過了敞临,如果未解析态辛,需要重新進行解析
            // 這里的AppConfig類向容器中添加的bean,實際上在parser.parse()這一步已經(jīng)全部被解析了
            // 所以為什么還需要做這個判斷挺尿,目前沒看懂奏黑,似乎沒有任何意義炊邦。

            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());

        // Register the ImportRegistry as a bean in order to support ImportAware @Configuration classes
        if (sbr != null && !sbr.containsSingleton(IMPORT_REGISTRY_BEAN_NAME)) {
            sbr.registerSingleton(IMPORT_REGISTRY_BEAN_NAME, parser.getImportRegistry());
        }

        if (this.metadataReaderFactory instanceof CachingMetadataReaderFactory) {
            // Clear cache in externally provided MetadataReaderFactory; this is a no-op
            // for a shared cache since it'll be cleared by the ApplicationContext.
            ((CachingMetadataReaderFactory) this.metadataReaderFactory).clearCache();
        }
    }
  • 遍歷注冊列表的BeanDefinition,如果是配置候選類(帶有注解:@Configuration熟史,@Bean馁害,@Component,@ComponentScan蹂匹,@Import碘菜,@ImportResource)則加入到列表中,如果沒有配置候選類怒详,直接返回
  • 對配置候選類排序
  • 生成配置類解析器
  • 進入while循環(huán)炉媒,解析配置候選類,如果在解析配置候選類的過程中加入了新的配置候選類昆烁,繼續(xù)解析吊骤,直至配置候選類解析完

7.ConfigurationClassParser#parse

    public void parse(Set<BeanDefinitionHolder> configCandidates) {
        for (BeanDefinitionHolder holder : configCandidates) {
            BeanDefinition bd = holder.getBeanDefinition();
            try {
                if (bd instanceof AnnotatedBeanDefinition) {
                    parse(((AnnotatedBeanDefinition) bd).getMetadata(), holder.getBeanName());
                }
                else if (bd instanceof AbstractBeanDefinition && ((AbstractBeanDefinition) bd).hasBeanClass()) {
                    parse(((AbstractBeanDefinition) bd).getBeanClass(), holder.getBeanName());
                }
                else {
                    parse(bd.getBeanClassName(), holder.getBeanName());
                }
            }
            catch (BeanDefinitionStoreException ex) {
                throw ex;
            }
            catch (Throwable ex) {
                throw new BeanDefinitionStoreException(
                        "Failed to parse configuration class [" + bd.getBeanClassName() + "]", ex);
            }
        }

        this.deferredImportSelectorHandler.process();
    }

8.ConfigurationClassParser#parse

    protected final void parse(AnnotationMetadata metadata, String beanName) throws IOException {
        processConfigurationClass(new ConfigurationClass(metadata, beanName), DEFAULT_EXCLUSION_FILTER);
    }

9.ConfigurationClassParser#processConfigurationClass

    protected void processConfigurationClass(ConfigurationClass configClass, Predicate<String> filter) 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, filter);
        do {
            sourceClass = doProcessConfigurationClass(configClass, sourceClass, filter);
        }
        while (sourceClass != null);

        this.configurationClasses.put(configClass, configClass);
    }

10.ConfigurationClassParser#doProcessConfigurationClass

    protected final SourceClass doProcessConfigurationClass(
            ConfigurationClass configClass, SourceClass sourceClass, Predicate<String> filter)
            throws IOException {

        // 1、首先處理內(nèi)部類静尼,處理內(nèi)部類時白粉,最終還是調(diào)用doProcessConfigurationClass()方法
        if (configClass.getMetadata().isAnnotated(Component.class.getName())) {
            // Recursively process any member (nested) classes first
            processMemberClasses(configClass, sourceClass, filter);
        }

        // Process any @PropertySource annotations
        // 2、處理屬性資源文件鼠渺,加了@PropertySource注解
        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");
            }
        }

        // Process any @ComponentScan annotations
        // 3鸭巴、處理@ComponentScan或者@ComponentScans注解
        // 3.1 先找出類上的@ComponentScan和@ComponentScans注解的所有屬性(例如basePackages等屬性值)
        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

                // 3.2 解析@ComponentScan和@ComponentScans配置的掃描的包所包含的類
                // 比如 basePackages = com.tiantang.study, 那么在這一步會掃描出這個包及子包下的class,然后將其解析成BeanDefinition
                // (BeanDefinition可以理解為等價于BeanDefinitionHolder)

                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

                // 3.3 通過上一步掃描包下的類拦盹,有可能掃描出來的bean中可能也添加了ComponentScan或者ComponentScans注解.
                //所以這里需要循環(huán)遍歷一次鹃祖,進行遞歸(parse),繼續(xù)解析普舆,直到解析出的類上沒有ComponentScan和ComponentScans
                // (這時3.1這一步解析出componentScans為空列表恬口,不會進入到if語句,遞歸終止)
                for (BeanDefinitionHolder holder : scannedBeanDefinitions) {
                    BeanDefinition bdCand = holder.getBeanDefinition().getOriginatingBeanDefinition();
                    if (bdCand == null) {
                        bdCand = holder.getBeanDefinition();
                    }
                    // 同樣沼侣,這里會調(diào)用ConfigurationClassUtils.checkConfigurationClassCandidate()方法來判斷類是否是一個配置類
                    if (ConfigurationClassUtils.checkConfigurationClassCandidate(bdCand, this.metadataReaderFactory)) {
                        parse(bdCand.getBeanClassName(), holder.getBeanName());
                    }
                }
            }
        }

        // Process any @Import annotations

        // 4.處理Import注解注冊的bean祖能,這一步只會將import注冊的bean變?yōu)镃onfigurationClass,不會變成BeanDefinition
        // 而是在loadBeanDefinitions()方法中變成BeanDefinition,再放入到BeanDefinitionMap中

        processImports(configClass, sourceClass, getImports(sourceClass), filter, true);

        // Process any @ImportResource annotations
        // 5.處理@ImportResource注解引入的配置文件
        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);
            }
        }

        // Process individual @Bean methods
        // 處理加了@Bean注解的方法
        Set<MethodMetadata> beanMethods = retrieveBeanMethodMetadata(sourceClass);
        for (MethodMetadata methodMetadata : beanMethods) {
            configClass.addBeanMethod(new BeanMethod(methodMetadata, configClass));
        }

        // Process default methods on interfaces
        processInterfaces(configClass, sourceClass);

        // 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;
    }
  • 處理內(nèi)部類蛾洛,最終還是要調(diào)用處理配置候選類
  • 處理@PropertySources养铸,@PropertySource注解類
  • 處理@ComponentScans,@ComponentScan注解類
  • 處理@Import注解類
  • 處理@ImportResource注解類
  • 處理@Bean注解的方法
  • 處理接口
  • 處理父類
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末轧膘,一起剝皮案震驚了整個濱河市钞螟,隨后出現(xiàn)的幾起案子,更是在濱河造成了極大的恐慌扶供,老刑警劉巖筛圆,帶你破解...
    沈念sama閱讀 217,185評論 6 503
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件,死亡現(xiàn)場離奇詭異椿浓,居然都是意外死亡太援,警方通過查閱死者的電腦和手機,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 92,652評論 3 393
  • 文/潘曉璐 我一進店門扳碍,熙熙樓的掌柜王于貴愁眉苦臉地迎上來提岔,“玉大人,你說我怎么就攤上這事笋敞〖蠲桑” “怎么了?”我有些...
    開封第一講書人閱讀 163,524評論 0 353
  • 文/不壞的土叔 我叫張陵夯巷,是天一觀的道長赛惩。 經(jīng)常有香客問我,道長趁餐,這世上最難降的妖魔是什么喷兼? 我笑而不...
    開封第一講書人閱讀 58,339評論 1 293
  • 正文 為了忘掉前任,我火速辦了婚禮后雷,結(jié)果婚禮上季惯,老公的妹妹穿的比我還像新娘。我一直安慰自己臀突,他們只是感情好勉抓,可當我...
    茶點故事閱讀 67,387評論 6 391
  • 文/花漫 我一把揭開白布。 她就那樣靜靜地躺著候学,像睡著了一般藕筋。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發(fā)上梳码,一...
    開封第一講書人閱讀 51,287評論 1 301
  • 那天隐圾,我揣著相機與錄音,去河邊找鬼边翁。 笑死翎承,一個胖子當著我的面吹牛,可吹牛的內(nèi)容都是我干的符匾。 我是一名探鬼主播叨咖,決...
    沈念sama閱讀 40,130評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼,長吁一口氣:“原來是場噩夢啊……” “哼啊胶!你這毒婦竟也來了甸各?” 一聲冷哼從身側(cè)響起,我...
    開封第一講書人閱讀 38,985評論 0 275
  • 序言:老撾萬榮一對情侶失蹤焰坪,失蹤者是張志新(化名)和其女友劉穎趣倾,沒想到半個月后,有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體某饰,經(jīng)...
    沈念sama閱讀 45,420評論 1 313
  • 正文 獨居荒郊野嶺守林人離奇死亡儒恋,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,617評論 3 334
  • 正文 我和宋清朗相戀三年善绎,在試婚紗的時候發(fā)現(xiàn)自己被綠了。 大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片诫尽。...
    茶點故事閱讀 39,779評論 1 348
  • 序言:一個原本活蹦亂跳的男人離奇死亡禀酱,死狀恐怖,靈堂內(nèi)的尸體忽然破棺而出牧嫉,到底是詐尸還是另有隱情剂跟,我是刑警寧澤,帶...
    沈念sama閱讀 35,477評論 5 345
  • 正文 年R本政府宣布酣藻,位于F島的核電站曹洽,受9級特大地震影響,放射性物質(zhì)發(fā)生泄漏辽剧。R本人自食惡果不足惜送淆,卻給世界環(huán)境...
    茶點故事閱讀 41,088評論 3 328
  • 文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望抖仅。 院中可真熱鬧坊夫,春花似錦、人聲如沸撤卢。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,716評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽放吩。三九已至智听,卻和暖如春,著一層夾襖步出監(jiān)牢的瞬間渡紫,已是汗流浹背到推。 一陣腳步聲響...
    開封第一講書人閱讀 32,857評論 1 269
  • 我被黑心中介騙來泰國打工, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留惕澎,地道東北人莉测。 一個月前我還...
    沈念sama閱讀 47,876評論 2 370
  • 正文 我出身青樓,卻偏偏與公主長得像唧喉,于是被迫代替她去往敵國和親捣卤。 傳聞我的和親對象是個殘疾皇子,可洞房花燭夜當晚...
    茶點故事閱讀 44,700評論 2 354

推薦閱讀更多精彩內(nèi)容