Nacos源码分析十、配置动态刷新（3）

前文提到RefreshScope中维护了一个map缓存，缓存的内容是包装原bean的BeanLifecycleWrapper，这个包装类具备销毁能力。当新的配置更新通知来后，我们只要能找到RefreshScope去销毁了对应的bean，那么再次使用时cglib的proxy就会重新去获取target类实例，然后重新实例化。

回到NacosContextRefresher类，看一下注册监听的代码：

private void registerNacosListener(final String groupKey, final String dataKey) {
   String key = NacosPropertySourceRepository.getMapKey(dataKey, groupKey);
   Listener listener = listenerMap.computeIfAbsent(key,
         lst -> new AbstractSharedListener() {
            @Override
            public void innerReceive(String dataId, String group,
                  String configInfo) {
               refreshCountIncrement();
               nacosRefreshHistory.addRefreshRecord(dataId, group, configInfo);
               // todo feature: support single refresh for listening
               applicationContext.publishEvent(
                     new RefreshEvent(this, null, "Refresh Nacos config"));
               if (log.isDebugEnabled()) {
                  log.debug(String.format(
                        "Refresh Nacos config group=%s,dataId=%s,configInfo=%s",
                        group, dataId, configInfo));
               }
            }
         });
   try {
      configService.addListener(dataKey, groupKey, listener);
   }
   catch (NacosException e) {
      log.warn(String.format(
            "register fail for nacos listener ,dataId=[%s],group=[%s]", dataKey,
            groupKey), e);
   }
}

当有配置变更时发布RefreshEvent事件，这个事件是RefreshEventListener监听的：

@Override
public void onApplicationEvent(ApplicationEvent event) {
   
   if (event instanceof ApplicationReadyEvent) {
   
      handle((ApplicationReadyEvent) event);
   }
   else if (event instanceof RefreshEvent)