Spring integration Spring集成：确保已初始化IntegrationRequestMappingHandlerMapping

IntegrationRequestMappingHandlerMapping

对

ContextRefreshedEvent

的初始化有特殊要求。引用代码：

@Override
public void afterPropertiesSet() {
    // No-op in favor of onApplicationEvent
}

/**
 * {@link HttpRequestHandlingEndpointSupport}s may depend on auto-created
 * {@code requestChannel}s, so MVC Handlers detection should be postponed
 * as late as possible.
 * @see RequestMappingHandlerMapping#afterPropertiesSet()
 */
@Override
public void onApplicationEvent(ContextRefreshedEvent event) {
    if (!this.initialized.getAndSet(true)) {
        super.afterPropertiesSet();
    }
}

其效果是，当其他bean在应用程序启动期间尝试对其进行评估时，其

mappingRegistry

为空，即使它们以

MAX\u值的阶段实现
SmartLifeCycle

在我的例子中，我尝试为实现一个spring集成插件。它的
DocumentationPluginsBootstrapper
需要访问请求映射来记录它们

在开始请求其映射之前，如何确保已初始化
IntegrationRequestMappingHandlerMapping
？监听
ContextRefreshedEvent
是否也是正确的方法，但是
@Order
的值较高？或者你会建议使用不同的活动吗

更新：AbstractHandlerMapping已使用Order.Lower\u优先级。我想我不能使用上下文刷新事件来保证安全

另请参见。
上下文刷新事件实际上是应用程序上下文初始化的最后一步：

            // Allows post-processing of the bean factory in context subclasses.
            postProcessBeanFactory(beanFactory);

            // Invoke factory processors registered as beans in the context.
            invokeBeanFactoryPostProcessors(beanFactory);

            // Register bean processors that intercept bean creation.
            registerBeanPostProcessors(beanFactory);

            // Initialize message source for this context.
            initMessageSource();

            // Initialize event multicaster for this context.
            initApplicationEventMulticaster();

            // Initialize other special beans in specific context subclasses.
            onRefresh();

            // Check for listener beans and register them.
            registerListeners();

            // Instantiate all remaining (non-lazy-init) singletons.
            finishBeanFactoryInitialization(beanFactory);

            // Last step: publish corresponding event.
            finishRefresh();

它是在
finishRefresh（）
中激发的

<>你确实应该考虑< <代码>应用程序> <代码> > <代码> >顺序。同时，框架注册
IntegrationRequestMappingHandlerMapping
，顺序==0

：

private void registerRequestMappingHandlerMappingIfNecessary(BeanDefinitionRegistry registry) {
    if (HttpContextUtils.WEB_MVC_PRESENT &&
            !registry.containsBeanDefinition(HttpContextUtils.HANDLER_MAPPING_BEAN_NAME)) {
        BeanDefinitionBuilder requestMappingBuilder =
                BeanDefinitionBuilder.genericBeanDefinition(IntegrationRequestMappingHandlerMapping.class);
        requestMappingBuilder.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
        requestMappingBuilder.addPropertyValue(IntegrationNamespaceUtils.ORDER, 0);
        registry.registerBeanDefinition(HttpContextUtils.HANDLER_MAPPING_BEAN_NAME,
                requestMappingBuilder.getBeanDefinition());
    }
}

因此，您真的需要保存以在自己的侦听器中处理映射。仅仅因为，由于

order=0

的缘故，

IntegrationRequestMappingHandlerMapping

将被初始化

这同样适用于

WebFluxIntegrationRequestMappingHandlerMapping

：

private void registerReactiveRequestMappingHandlerMappingIfNecessary(BeanDefinitionRegistry registry) {
    if (HttpContextUtils.WEB_FLUX_PRESENT &&
            !registry.containsBeanDefinition(WebFluxContextUtils.HANDLER_MAPPING_BEAN_NAME)) {
        BeanDefinitionBuilder requestMappingBuilder =
                BeanDefinitionBuilder.genericBeanDefinition(WebFluxIntegrationRequestMappingHandlerMapping.class);
        requestMappingBuilder.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
        requestMappingBuilder.addPropertyValue(IntegrationNamespaceUtils.ORDER, 0);
        registry.registerBeanDefinition(WebFluxContextUtils.HANDLER_MAPPING_BEAN_NAME,
                requestMappingBuilder.getBeanDefinition());

        BeanDefinitionReaderUtils.registerWithGeneratedName(
                new RootBeanDefinition(IntegrationHandlerResultHandler.class), registry);
    }
}

---

是否可以添加在IntegrationRequestHandlerMapping和WebFluxIntegrationRequestMappingHandlerMapping完成ContextRefreshedEvent处理后激发的应用程序事件，如事件IntegrationRequestHandlerMappingReadyEvent？