Package org.springframework.integration.webflux.inbound

Class WebFluxIntegrationRequestMappingHandlerMapping

java.lang.Object
org.springframework.context.support.ApplicationObjectSupport
org.springframework.web.reactive.handler.AbstractHandlerMapping
org.springframework.web.reactive.result.method.AbstractHandlerMethodMapping<RequestMappingInfo>
org.springframework.web.reactive.result.method.RequestMappingInfoHandlerMapping
org.springframework.web.reactive.result.method.annotation.RequestMappingHandlerMapping
org.springframework.integration.webflux.inbound.WebFluxIntegrationRequestMappingHandlerMapping
All Implemented Interfaces:
EventListener, Aware, BeanNameAware, BeanPostProcessor, DestructionAwareBeanPostProcessor, InitializingBean, ApplicationContextAware, ApplicationListener<ContextRefreshedEvent>, EmbeddedValueResolverAware, Ordered, HandlerMapping
public class WebFluxIntegrationRequestMappingHandlerMapping
extends RequestMappingHandlerMapping
implements ApplicationListener<ContextRefreshedEvent>, DestructionAwareBeanPostProcessor
The HandlerMapping implementation that detects and registers RequestMappingInfos for HttpRequestHandlingEndpointSupport from a Spring Integration HTTP configuration of <inbound-channel-adapter/> and <inbound-gateway/> elements.

This class is automatically configured as a bean in the application context during the parsing phase of the <inbound-gateway/> elements, if there is none registered, yet. However it can be configured as a regular bean with appropriate configuration for RequestMappingHandlerMapping. It is recommended to have only one similar bean in the application context using the 'id' WebFluxContextUtils.HANDLER_MAPPING_BEAN_NAME.

In most cases, Spring MVC offers to configure Request Mapping via org.springframework.stereotype.Controller and RequestMapping. That's why Spring MVC's Handler Mapping infrastructure relies on HandlerMethod, as different methods at the same org.springframework.stereotype.Controller user-class may have their own RequestMapping. On the other side, all Spring Integration HTTP Inbound Endpoints are configured on the basis of the same HttpRequestHandlingEndpointSupport class and there is no single RequestMappingInfo configuration without HandlerMethod in Spring MVC. Accordingly WebFluxIntegrationRequestMappingHandlerMapping is a HandlerMapping compromise implementation between method-level annotations and component-level (e.g. Spring Integration XML) configurations.

Starting with version 5.1, this class implements DestructionAwareBeanPostProcessor to register HTTP endpoints at runtime for dynamically declared beans, e.g. via IntegrationFlowContext, and unregister them during the WebFluxInboundEndpoint destruction.

Since:
5.0
Author:
Artem Bilan, Gary Russell
See Also:
RequestMapping, RequestMappingHandlerMapping