在ApplicationContext刷新獲取beanFactory之后法希，開始準(zhǔn)備context使用的beanFactory昌妹。這一步相對比較簡單议忽，就是配置facotry的特性恃鞋，比如：ClassLoader躲撰，post-processors等等

代碼如下：

protected void prepareBeanFactory(ConfigurableListableBeanFactory beanFactory) {
        // Tell the internal bean factory to use the context's class loader etc.
        //讓BeanFactory使用context的class loader
        beanFactory.setBeanClassLoader(getClassLoader());
        beanFactory.setBeanExpressionResolver(new StandardBeanExpressionResolver(beanFactory.getBeanClassLoader()));
        beanFactory.addPropertyEditorRegistrar(new ResourceEditorRegistrar(this, getEnvironment()));

        // Configure the bean factory with context callbacks.
        // 配置bean factory的context回調(diào)
        beanFactory.addBeanPostProcessor(new ApplicationContextAwareProcessor(this));
        beanFactory.ignoreDependencyInterface(ResourceLoaderAware.class);
        beanFactory.ignoreDependencyInterface(ApplicationEventPublisherAware.class);
        beanFactory.ignoreDependencyInterface(MessageSourceAware.class);
        beanFactory.ignoreDependencyInterface(ApplicationContextAware.class);
        beanFactory.ignoreDependencyInterface(EnvironmentAware.class);

        // BeanFactory interface not registered as resolvable type in a plain factory.
        // MessageSource registered (and found for autowiring) as a bean.
        beanFactory.registerResolvableDependency(BeanFactory.class, beanFactory);
        beanFactory.registerResolvableDependency(ResourceLoader.class, this);
        beanFactory.registerResolvableDependency(ApplicationEventPublisher.class, this);
        beanFactory.registerResolvableDependency(ApplicationContext.class, this);

        // Detect a LoadTimeWeaver and prepare for weaving, if found.
        if (beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
            beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
            // Set a temporary ClassLoader for type matching.
            beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
        }

        // Register default environment beans.
        // 注冊默認的environment bean
        if (!beanFactory.containsLocalBean(ENVIRONMENT_BEAN_NAME)) {
            beanFactory.registerSingleton(ENVIRONMENT_BEAN_NAME, getEnvironment());
        }
        if (!beanFactory.containsLocalBean(SYSTEM_PROPERTIES_BEAN_NAME)) {
            beanFactory.registerSingleton(SYSTEM_PROPERTIES_BEAN_NAME, getEnvironment().getSystemProperties());
        }
        if (!beanFactory.containsLocalBean(SYSTEM_ENVIRONMENT_BEAN_NAME)) {
            beanFactory.registerSingleton(SYSTEM_ENVIRONMENT_BEAN_NAME, getEnvironment().getSystemEnvironment());
        }
    }

分析

beanfactory的準(zhǔn)備階段精偿，比較簡單弧圆，主要明白準(zhǔn)備階段操作的幾個方法。

beanFactory.addBeanPostProcessor

添加BeanPostProcessor笔咽，當(dāng)bean被這個工廠創(chuàng)建的時候會用到PostProcessor, 在beanfactory中存儲了beanPostProcessors的列表搔预，在生效的時候，列表中的PostProcessor都會執(zhí)行叶组。

        beanFactory.addBeanPostProcessor(new ApplicationContextAwareProcessor(this));

beanFactory.ignoreDependencyInterface(Class<?> ifc)

在注入的時候忽略此方法指定的接口類拯田。也就是指定的接口不會被注入進去。

如下甩十，不會生效

@Autowire 
ResourceLoaderAware aware;

        beanFactory.ignoreDependencyInterface(ResourceLoaderAware.class);
        beanFactory.ignoreDependencyInterface(ApplicationEventPublisherAware.class);
        beanFactory.ignoreDependencyInterface(MessageSourceAware.class);
        beanFactory.ignoreDependencyInterface(ApplicationContextAware.class);
        beanFactory.ignoreDependencyInterface(EnvironmentAware.class);

beanFactory.registerResolvableDependency(Class<?> dependencyType, Object autowiredValue)

注冊可以解析的依賴關(guān)系船庇，當(dāng)注入的類型為dependencyType的時候，注入autowiredValue侣监。
注入類型與注入值的關(guān)系存儲在map中鸭轮。

resolvableDependencies = new ConcurrentHashMap<Class<?>, Object>(16);

// 注入類型為BeanFactory時，注入beanFactory(DefaultListableBeanFactory)
beanFactory.registerResolvableDependency(BeanFactory.class, beanFactory);
        beanFactory.registerResolvableDependency(ResourceLoader.class, this);

//注入類型為ApplicationEventPublisher時橄霉，注入值為this(ApplicationContext)
beanFactory.registerResolvableDependency(ApplicationEventPublisher.class, this);

//注入類型為ApplicationContext時窃爷，注入值也為this(ApplicationContext)
beanFactory.registerResolvableDependency(ApplicationContext.class, this);

額外

prepareBeanFactory主要做一些準(zhǔn)備工作，沒有什么邏輯，在Applicationcontext的refresh方法中往下看一步按厘，執(zhí)行

postProcessBeanFactory(beanFactory);

這一步Spring框架中沒有實現(xiàn)医吊，留待我們自己實現(xiàn)。

最后

這次看了refresh方法中的prepareBeanFactory內(nèi)容比較簡單逮京，就不多說了卿堂。