WebFluxConfigurer

All Known Implementing Classes:

DefaultControllerSpec.TestWebFluxConfigurer, WebFluxConfigurerComposite
```
public interface WebFluxConfigurer
```
Defines callback methods to customize the configuration for Web Reactive 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

All Methods Instance Methods Default Methods
Modifier and Type	Method and Description
`default void`	`addArgumentResolvers(java.util.List<HandlerMethodArgumentResolver> resolvers)` Provide custom controller method argument resolvers.
`default void`	`addCorsMappings(CorsRegistry registry)` Configure cross origin requests processing.
`default void`	`addFormatters(FormatterRegistry registry)` Add custom `Converter`s and `Formatter`s for performing type conversion and formatting of controller method arguments.
`default void`	`addResourceHandlers(ResourceHandlerRegistry registry)` Add resource handlers for serving static resources.
`default void`	`configureContentTypeResolver(RequestedContentTypeResolverBuilder builder)` Configure how the content type requested for the response is resolved.
`default void`	`configureMessageReaders(java.util.List<HttpMessageReader<?>> readers)` Configure the message readers to use for decoding the request body where `@RequestBody` and `HttpEntity` controller method arguments are used.
`default void`	`configureMessageWriters(java.util.List<HttpMessageWriter<?>> writers)` Configure the message writers to use to encode the response body based on the return values of `@ResponseBody`, and `ResponseEntity` controller methods.
`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 void`	`extendMessageReaders(java.util.List<HttpMessageReader<?>> readers)` An alternative to `configureMessageReaders(List)` that allows modifying the message readers to use after default ones have been added.
`default void`	`extendMessageWriters(java.util.List<HttpMessageWriter<?>> writers)` An alternative to `configureMessageWriters(List)` that allows modifying the message writers to use after default ones have been added.
`default java.util.Optional<MessageCodesResolver>`	`getMessageCodesResolver()` Provide a custom `MessageCodesResolver` to use for data binding instead of the one created by default in `DataBinder`.
`default java.util.Optional<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.
    The given builder will create a composite of multiple RequestedContentTypeResolvers, each defining a way to resolve the requested content type (accept HTTP header, path extension, parameter, etc).
    
    Parameters:
    
    builder - factory that creates a CompositeContentTypeResolver
  - addCorsMappings
```
default void addCorsMappings(CorsRegistry registry)
```
    Configure cross origin requests processing.
    
    See Also:
    
    CorsRegistry
  - configurePathMatching
```
default void configurePathMatching(PathMatchConfigurer configurer)
```
    Configure path matching options.
    The given configurer assists with configuring 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
  - addArgumentResolvers
```
default void addArgumentResolvers(java.util.List<HandlerMethodArgumentResolver> resolvers)
```
    Provide custom controller method argument resolvers. Such resolvers do not override and will be invoked after the built-in ones.
    
    Parameters:
    
    resolvers - a list of resolvers to add
  - configureMessageReaders
```
default void configureMessageReaders(java.util.List<HttpMessageReader<?>> readers)
```
    Configure the message readers to use for decoding the request body where @RequestBody and HttpEntity controller method arguments are used. If none are specified, default ones are added based on WebFluxConfigurationSupport.addDefaultHttpMessageReaders(java.util.List<org.springframework.http.codec.HttpMessageReader<?>>).
    See extendMessageReaders(List) for adding readers in addition to the default ones.
    
    Parameters:
    
    readers - an empty list to add message readers to
  - extendMessageReaders
```
default void extendMessageReaders(java.util.List<HttpMessageReader<?>> readers)
```
    An alternative to configureMessageReaders(List) that allows modifying the message readers to use after default ones have been added.
  - addFormatters
```
default void addFormatters(FormatterRegistry registry)
```
    Add custom Converters and Formatters for performing type conversion and formatting of controller method arguments.
  - getValidator
```
default java.util.Optional<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
```
default java.util.Optional<MessageCodesResolver> getMessageCodesResolver()
```
    Provide a custom MessageCodesResolver to use for data binding instead of the one created by default in DataBinder.
  - configureMessageWriters
```
default void configureMessageWriters(java.util.List<HttpMessageWriter<?>> writers)
```
    Configure the message writers to use to encode the response body based on the return values of @ResponseBody, and ResponseEntity controller methods. If none are specified, default ones are added based on WebFluxConfigurationSupport.addDefaultHttpMessageWriters(List).
    See extendMessageWriters(List) for adding writers in addition to the default ones.
    
    Parameters:
    
    writers - a empty list to add message writers to
  - extendMessageWriters
```
default void extendMessageWriters(java.util.List<HttpMessageWriter<?>> writers)
```
    An alternative to configureMessageWriters(List) that allows modifying the message writers to use after default ones have been added.
  - 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

Interface WebFluxConfigurer

Method Summary

Method Detail

configureContentTypeResolver

addCorsMappings

configurePathMatching

addResourceHandlers

addArgumentResolvers

configureMessageReaders

extendMessageReaders

addFormatters

getValidator

getMessageCodesResolver

configureMessageWriters

extendMessageWriters

configureViewResolvers