getSingleton 和popu lateBean 解析

LD is tigger forever，CG are not brothers forever， throw the pot and shine forever.
Modesty is not false, solid is not naive, treacherous but not deceitful, stay with good people, and stay away from poor people.
talk is cheap, show others the code,Keep progress，make a better result.
Survive during the day and develop at night。

目录

概述

实现思路分析

getSingleton 源码分析

refresh方法中调用了10个左右的方法，具体方法不一一细看，看今天分析的重点方法finishBeanFactoryInitialization方法，
在该方法中又调用了preInstantiateSingletons()方法，这个方法才是今天的主角，在该方法中会生成所有非懒加载的单例bean。方法定义如下，

@Override
    public void preInstantiateSingletons() throws BeansException {
        if (logger.isTraceEnabled()) {
            logger.trace("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<>(this.beanDefinitionNames);
 
        // Trigger initialization of all non-lazy singleton beans...
        for (String beanName : beanNames) {
            RootBeanDefinition bd = getMergedLocalBeanDefinition(beanName);
            if (!bd.isAbstract() && bd.isSingleton() && !bd.isLazyInit()) {
                if (isFactoryBean(beanName)) {
                    Object bean = getBean(FACTORY_BEAN_PREFIX + beanName);
                    if (bean instanceof FactoryBean) {
                        final FactoryBean<?> factory = (FactoryBean<?>) bean;
                        boolean isEagerInit;
                        if (System.getSecurityManager() != null && factory instanceof SmartFactoryBean) {
                            isEagerInit = AccessController.doPrivileged((PrivilegedAction<Boolean>)
                                            ((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((PrivilegedAction<Object>) () -> {
                        smartSingleton.afterSingletonsInstantiated();
                        return null;
                    }, getAccessControlContext());
                }
                else {
                    smartSingleton.afterSingletonsInstantiated();
                }
            }
        }
    }

该方法完成的主要逻辑是遍历所有的beanName，调用getBean(beanName)方法生成单例bean，在遍历过程中对FactoryBean做了特殊的判断，大家都知道FactoryBean是一种特殊的bean，
重点看getBean(beanName)方法，getBean(beanName)方法调用了doGetBean(beanName)方法

@Override
    public Object getBean(String name) throws BeansException {
        return doGetBean(name, null, null, false);
    }

doGetBean方法中有getSingleton、getObjectForBeanInstance、createBean等方法是很重要的。
在doGetBean方法中首先调用getSingleton方法检查单例缓存中是否有该bean，如果没有则判断当前bean的作用域是单例（singleton）还是原型（prototype），如果是单例的，再次调用getSingleton方法，不过这次的该方法是重载的一个；如果是原型的则调用createBean方法生成bean，
对singletonObject、earlySingletonObjects、singletonFactories逐级判断，其中singletonFactories中存储的是提前暴露的实例工厂，用来生成一个实例或者实例的代理类。

Bean 定义的方法

Bean 实例化之后
Bean对象的依赖的关系设置好
BeanDefinition 解析
Bean对象创建完成之后的，怎样设置好Bean对象的依赖关系完成整个依赖注入过程，在完成依赖注入的过程中的依据是对BeanDefinition对象的解析

popu lateBean 解析

这篇文章就是在分析Bean对象完成之后的，怎么样设置bean对象的依赖关系完成整个依赖关系注入流程，在完成依赖注入的过程中的依据是对BeanDefinnation 对象的解析。
populateBean，这个方法是位于这个方法是位于AbstractAutowireCapableBeanFactory类中populateBean方法中的源码：

//这个方法的具体作用等待解析
protected void populateBean(String beanName, RootBeanDefinition mbd, @Nullable BeanWrapper bw) {
     //解析之后的BeanDefiinition如果为空,其结果还有propertyValues值就会抛出异常
        if (bw == null) {
            if (mbd.hasPropertyValues()) {
                throw new BeanCreationException(mbd.getResourceDescription(), beanName, "Cannot apply property values to null instance");
            }
        } else {
            //否则就会就会调用bean的后置处理器遍历
            boolean continueWithPropertyPopulation = true;
            if (!mbd.isSynthetic() && this.hasInstantiationAwareBeanPostProcessors()) {
                Iterator var5 = this.getBeanPostProcessors().iterator();

                //这段代码主要就是看迭代器中是否有instance对象的值，有的话就会将标识符变为false
                while(var5.hasNext()) {
                    //强制转换为BeanPostProcecssor
                    BeanPostProcessor bp = (BeanPostProcessor)var5.next();
                    if (bp instanceof InstantiationAwareBeanPostProcessor) {
                     
                        InstantiationAwareBeanPostProcessor ibp = (InstantiationAwareBeanPostProcessor)bp;
                        if (!ibp.postProcessAfterInstantiation(bw.getWrappedInstance(), beanName)) {
                            continueWithPropertyPopulation = false;
                            break;
                        }
                    }
                }
            }

            //这里是对标识符结果进行
            if (continueWithPropertyPopulation) {
                PropertyValues pvs = mbd.hasPropertyValues() ? mbd.getPropertyValues() : null;
                //开始进行依赖注入的过程，处理Autowire的注入
                if (mbd.getResolvedAutowireMode() == 1 || mbd.getResolvedAutowireMode() == 2) {
                    MutablePropertyValues newPvs = new MutablePropertyValues((PropertyValues)pvs);
                    if (mbd.getResolvedAutowireMode() == 1) {
                        this.autowireByName(beanName, mbd, bw, newPvs);
                    }

                    if (mbd.getResolvedAutowireMode() == 2) {
                        this.autowireByType(beanName, mbd, bw, newPvs);
                    }
                    
                    //这里对变量进行重定义
                    pvs = newPvs;
                }

                boolean hasInstAwareBpps = this.hasInstantiationAwareBeanPostProcessors();
                boolean needsDepCheck = mbd.getDependencyCheck() != 0;
                PropertyDescriptor[] filteredPds = null;
                //如果有bean后置处理器时，并且结果为null值，那么就会直接从BeanDefinition中直接调用方法获取
                if (hasInstAwareBpps) {
                    if (pvs == null) {
                        pvs = mbd.getPropertyValues();
                    }

                    //遍历后置处理器的迭代器代码
                    Iterator var9 = this.getBeanPostProcessors().iterator();

                    while(var9.hasNext()) {
                        BeanPostProcessor bp = (BeanPostProcessor)var9.next();
                        if (bp instanceof InstantiationAwareBeanPostProcessor) {
                            InstantiationAwareBeanPostProcessor ibp = (InstantiationAwareBeanPostProcessor)bp;
                            //获取到propertyValues中的值
                            PropertyValues pvsToUse = ibp.postProcessProperties((PropertyValues)pvs, bw.getWrappedInstance(), beanName);
                            if (pvsToUse == null) {
                                if (filteredPds == null) {
                                    //获取到依赖的检查的过滤器
                                    filteredPds = this.filterPropertyDescriptorsForDependencyCheck(bw, mbd.allowCaching);
                                }

                                pvsToUse = ibp.postProcessPropertyValues((PropertyValues)pvs, filteredPds, bw.getWrappedInstance(), beanName);
                                if (pvsToUse == null) {
                                    return;
                                }
                            }

                            pvs = pvsToUse;
                        }
                    }
                }

                if (needsDepCheck) {
                    if (filteredPds == null) {
                        
                        filteredPds = this.filterPropertyDescriptorsForDependencyCheck(bw, mbd.allowCaching);
                    }

                    this.checkDependencies(beanName, mbd, filteredPds, (PropertyValues)pvs);
                }

                if (pvs != null) {
                    //对属性进行注入
                    this.applyPropertyValues(beanName, mbd, bw, (PropertyValues)pvs);
                }

            }
        }
    }

相关工具如下：

分析：

小结：

主要讲述了@PostConstruct，InitializingBean, 里面有许多不足，请大家指正~

参考资料和推荐阅读

1.链接: 参考资料.
2.链接: 参考资料.