org.springframework.web.reactive.config

Interface WebFluxConfigurer

All Known Implementing Classes:

WebFluxConfigurerComposite

public interface WebFluxConfigurer

Defines callback methods to customize the configuration for WebFlux applications enabled via @EnableWebFlux.

@EnableWebFlux-annotated configuration classes may implement this interface to be called back and given a chance to customize the default configuration. Consider implementing this interface and overriding the relevant methods for your needs.

Since:

5.0

Author:

Brian Clozel, Rossen Stoyanchev

Method Summary

Modifier and Type	Method and Description
default void	addCorsMappings(CorsRegistry registry) Configure cross origin requests processing.
default void	addFormatters(FormatterRegistry registry) Add custom Converters and Formatters for performing type conversion and formatting of controller method arguments.
default void	addResourceHandlers(ResourceHandlerRegistry registry) Add resource handlers for serving static resources.
default void	configureArgumentResolvers(ArgumentResolverConfigurer configurer) Configure resolvers for custom controller method arguments.
default void	configureContentTypeResolver(RequestedContentTypeResolverBuilder builder) Configure how the content type requested for the response is resolved.
default void	configureHttpMessageCodecs(ServerCodecConfigurer configurer) Configure custom HTTP message readers and writers or override built-in ones.
default void	configurePathMatching(PathMatchConfigurer configurer) Configure path matching options.
default void	configureViewResolvers(ViewResolverRegistry registry) Configure view resolution for processing the return values of controller methods that rely on resolving a View to render the response with.
default MessageCodesResolver	getMessageCodesResolver() Provide a custom MessageCodesResolver to use for data binding instead of the one created by default in DataBinder.
default Validator	getValidator() Provide a custom Validator.

Method Detail

configureContentTypeResolver

default void configureContentTypeResolver(RequestedContentTypeResolverBuilder builder)

Configure how the content type requested for the response is resolved.

Parameters:

builder - for configuring the resolvers to use

addCorsMappings

default void addCorsMappings(CorsRegistry registry)

Configure cross origin requests processing.

See Also:

CorsRegistry

configurePathMatching

default void configurePathMatching(PathMatchConfigurer configurer)

Configure path matching options. HandlerMappings with path matching options.

Parameters:

configurer - the PathMatchConfigurer instance

addResourceHandlers

default void addResourceHandlers(ResourceHandlerRegistry registry)

Add resource handlers for serving static resources.

See Also:

ResourceHandlerRegistry

configureArgumentResolvers

default void configureArgumentResolvers(ArgumentResolverConfigurer configurer)

Configure resolvers for custom controller method arguments.

Parameters:

configurer - to configurer to use

configureHttpMessageCodecs

default void configureHttpMessageCodecs(ServerCodecConfigurer configurer)

Configure custom HTTP message readers and writers or override built-in ones.

Parameters:

configurer - the configurer to use

addFormatters

default void addFormatters(FormatterRegistry registry)

Add custom Converters and Formatters for performing type conversion and formatting of controller method arguments.

getValidator

@Nullable
default Validator getValidator()

Provide a custom Validator.

By default a validator for standard bean validation is created if bean validation api is present on the classpath.

getMessageCodesResolver

@Nullable
default MessageCodesResolver getMessageCodesResolver()

Provide a custom MessageCodesResolver to use for data binding instead of the one created by default in DataBinder.

configureViewResolvers

default void configureViewResolvers(ViewResolverRegistry registry)

Configure view resolution for processing the return values of controller methods that rely on resolving a View to render the response with. By default all controller methods rely on view resolution unless annotated with @ResponseBody or explicitly return ResponseEntity. A view may be specified explicitly with a String return value or implicitly, e.g. void return value.

See Also:

ViewResolverRegistry