Spring Bean生命周期initMessageSource&initApplicationEventMulticaster(八)

作者 : 开心源码 本文共3804个字,预计阅读时间需要10分钟 发布时间: 2022-05-13 共291人阅读

现在到了ApplicationContext的refresh()方法中初始化消息源与事件广播器,这两个方法比较像,并且逻辑较少,放在一起看看。

initMessageSource

判断beanFactory中能否有名字为messageSource的bean,假如有,从beanFactory中获取并且判断获取的是不是HierarchicalMessageSource类型的,假如是设置其父级消息源

假如没有,新建DelegatingMessageSource类作为messageSource的Bean。

protected void initMessageSource() {      //获取BeanFactory        ConfigurableListableBeanFactory beanFactory = getBeanFactory();                //判断beanFactory中能否有名字为messageSource的bean        // MESSAGE_SOURCE_BEAN_NAME = "messageSource";        // 假如没有,新建DelegatingMessageSource类作为messageSource的Bean。        // 假如有,从beanFactory中获取                if (beanFactory.containsLocalBean(MESSAGE_SOURCE_BEAN_NAME)) {            this.messageSource = beanFactory.getBean(MESSAGE_SOURCE_BEAN_NAME, MessageSource.class);            // Make MessageSource aware of parent MessageSource.            if (this.parent != null && this.messageSource instanceof HierarchicalMessageSource) {                HierarchicalMessageSource hms = (HierarchicalMessageSource) this.messageSource;                if (hms.getParentMessageSource() == null) {                    // Only set parent context as parent MessageSource if no parent MessageSource                    // registered already.                    hms.setParentMessageSource(getInternalParentMessageSource());                }            }            if (logger.isDebugEnabled()) {                logger.debug("Using MessageSource [" + this.messageSource + "]");            }        }        else {            // Use empty MessageSource to be able to accept getMessage calls.            DelegatingMessageSource dms = new DelegatingMessageSource();            dms.setParentMessageSource(getInternalParentMessageSource());            this.messageSource = dms;            beanFactory.registerSingleton(MESSAGE_SOURCE_BEAN_NAME, this.messageSource);            if (logger.isDebugEnabled()) {                logger.debug("Unable to locate MessageSource with name '" + MESSAGE_SOURCE_BEAN_NAME +                        "': using default [" + this.messageSource + "]");            }        }    }

initApplicationEventMulticaster

初始化ApplicationEventMulticaster,假如beanFactory中不存在的话使用SimpleApplicationEventMulticaster,假如存在使用从beanFactory中获取的。

protected void initApplicationEventMulticaster() {        ConfigurableListableBeanFactory beanFactory = getBeanFactory();        //APPLICATION_EVENT_MULTICASTER_BEAN_NAME = "applicationEventMulticaster";        if (beanFactory.containsLocalBean(APPLICATION_EVENT_MULTICASTER_BEAN_NAME)) {            this.applicationEventMulticaster =                    beanFactory.getBean(APPLICATION_EVENT_MULTICASTER_BEAN_NAME, ApplicationEventMulticaster.class);            if (logger.isDebugEnabled()) {                logger.debug("Using ApplicationEventMulticaster [" + this.applicationEventMulticaster + "]");            }        }        else {            this.applicationEventMulticaster = new SimpleApplicationEventMulticaster(beanFactory);            beanFactory.registerSingleton(APPLICATION_EVENT_MULTICASTER_BEAN_NAME, this.applicationEventMulticaster);            if (logger.isDebugEnabled()) {                logger.debug("Unable to locate ApplicationEventMulticaster with name '" +                        APPLICATION_EVENT_MULTICASTER_BEAN_NAME +                        "': using default [" + this.applicationEventMulticaster + "]");            }        }    }

onRefresh

再多说一个onrefresh方法,这个在Spring框架中是没有实现的,留待我们继承可用来在实例化Singleton之前,实例化少量特殊的bean。

registerListeners

这个方法再refresh中也比较简单,都顺便记录下。

  1. 获取ApplicationContext初始化的listeners,而后增加到EventMulticaster,这个刚才初始化的,假如为空为SimpleApplicationEventMulticaster的那个
  2. 从BeanFactory中获取ApplicationListener类型的Bean,并且增加为ListenerBeans
  3. 有些事件可能要提前发出,将需要提前发出的事件发出并置空。
protected void registerListeners() {        // Register statically specified listeners first.        for (ApplicationListener<?> listener : getApplicationListeners()) {            getApplicationEventMulticaster().addApplicationListener(listener);        }        // Do not initialize FactoryBeans here: We need to leave all regular beans        // uninitialized to let post-processors apply to them!        String[] listenerBeanNames = getBeanNamesForType(ApplicationListener.class, true, false);        for (String listenerBeanName : listenerBeanNames) {            getApplicationEventMulticaster().addApplicationListenerBean(listenerBeanName);        }        // Publish early application events now that we finally have a multicaster...        Set<ApplicationEvent> earlyEventsToProcess = this.earlyApplicationEvents;        this.earlyApplicationEvents = null;        if (earlyEventsToProcess != null) {            for (ApplicationEvent earlyEvent : earlyEventsToProcess) {                getApplicationEventMulticaster().multicastEvent(earlyEvent);            }        }    }

TODO

  • AbstractApplicationEventMulticaster类的详细设计

最后

这几个方法比较简单,一起看看

说明
1. 本站所有资源来源于用户上传和网络,如有侵权请邮件联系站长!
2. 分享目的仅供大家学习和交流,您必须在下载后24小时内删除!
3. 不得使用于非法商业用途,不得违反国家法律。否则后果自负!
4. 本站提供的源码、模板、插件等等其他资源,都不包含技术服务请大家谅解!
5. 如有链接无法下载、失效或广告,请联系管理员处理!
6. 本站资源售价只是摆设,本站源码仅提供给会员学习使用!
7. 如遇到加密压缩包,请使用360解压,如遇到无法解压的请联系管理员
开心源码网 » Spring Bean生命周期initMessageSource&initApplicationEventMulticaster(八)

发表回复