public class WebFluxConfigurerComposite extends java.lang.Object implements WebFluxConfigurer
WebFluxConfigurer that delegates to one or more others.| Modifier and Type | Field and Description |
|---|---|
private java.util.List<WebFluxConfigurer> |
delegates |
| Constructor and Description |
|---|
WebFluxConfigurerComposite() |
| Modifier and Type | Method and Description |
|---|---|
void |
addArgumentResolvers(java.util.List<HandlerMethodArgumentResolver> resolvers)
Provide custom controller method argument resolvers.
|
void |
addCorsMappings(CorsRegistry registry)
Configure cross origin requests processing.
|
void |
addFormatters(FormatterRegistry registry)
|
void |
addResourceHandlers(ResourceHandlerRegistry registry)
Add resource handlers for serving static resources.
|
void |
addWebFluxConfigurers(java.util.List<WebFluxConfigurer> configurers) |
void |
configureContentTypeResolver(RequestedContentTypeResolverBuilder builder)
Configure how the content type requested for the response is resolved.
|
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. |
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. |
void |
configurePathMatching(PathMatchConfigurer configurer)
Configure path matching options.
|
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. |
private <T> java.util.Optional<T> |
createSingleBean(java.util.function.Function<WebFluxConfigurer,java.util.Optional<T>> factory,
java.lang.Class<T> beanType) |
void |
extendMessageReaders(java.util.List<HttpMessageReader<?>> readers)
An alternative to
WebFluxConfigurer.configureMessageReaders(List) that allows
modifying the message readers to use after default ones have been added. |
void |
extendMessageWriters(java.util.List<HttpMessageWriter<?>> writers)
An alternative to
WebFluxConfigurer.configureMessageWriters(List) that allows
modifying the message writers to use after default ones have been added. |
java.util.Optional<MessageCodesResolver> |
getMessageCodesResolver()
Provide a custom
MessageCodesResolver to use for data binding
instead of the one created by default in
DataBinder. |
java.util.Optional<Validator> |
getValidator()
Provide a custom
Validator. |
private final java.util.List<WebFluxConfigurer> delegates
public void addWebFluxConfigurers(java.util.List<WebFluxConfigurer> configurers)
public void configureContentTypeResolver(RequestedContentTypeResolverBuilder builder)
WebFluxConfigurerThe 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).
configureContentTypeResolver in interface WebFluxConfigurerbuilder - factory that creates a CompositeContentTypeResolverpublic void addCorsMappings(CorsRegistry registry)
WebFluxConfigureraddCorsMappings in interface WebFluxConfigurerCorsRegistrypublic void configurePathMatching(PathMatchConfigurer configurer)
WebFluxConfigurerThe given configurer assists with configuring
HandlerMappings with path matching options.
configurePathMatching in interface WebFluxConfigurerconfigurer - the PathMatchConfigurer instancepublic void addResourceHandlers(ResourceHandlerRegistry registry)
WebFluxConfigureraddResourceHandlers in interface WebFluxConfigurerResourceHandlerRegistrypublic void addArgumentResolvers(java.util.List<HandlerMethodArgumentResolver> resolvers)
WebFluxConfigureraddArgumentResolvers in interface WebFluxConfigurerresolvers - a list of resolvers to addpublic void configureMessageReaders(java.util.List<HttpMessageReader<?>> readers)
WebFluxConfigurer@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 WebFluxConfigurer.extendMessageReaders(List) for adding readers
in addition to the default ones.
configureMessageReaders in interface WebFluxConfigurerreaders - an empty list to add message readers topublic void extendMessageReaders(java.util.List<HttpMessageReader<?>> readers)
WebFluxConfigurerWebFluxConfigurer.configureMessageReaders(List) that allows
modifying the message readers to use after default ones have been added.extendMessageReaders in interface WebFluxConfigurerpublic void addFormatters(FormatterRegistry registry)
WebFluxConfigurerConverters and Formatters for performing type
conversion and formatting of controller method arguments.addFormatters in interface WebFluxConfigurerpublic java.util.Optional<Validator> getValidator()
WebFluxConfigurerValidator.
By default a validator for standard bean validation is created if bean validation api is present on the classpath.
getValidator in interface WebFluxConfigurerpublic java.util.Optional<MessageCodesResolver> getMessageCodesResolver()
WebFluxConfigurerMessageCodesResolver to use for data binding
instead of the one created by default in
DataBinder.getMessageCodesResolver in interface WebFluxConfigurerpublic void configureMessageWriters(java.util.List<HttpMessageWriter<?>> writers)
WebFluxConfigurer@ResponseBody, and ResponseEntity
controller methods. If none are specified, default ones are added based on
WebFluxConfigurationSupport.addDefaultHttpMessageWriters(List).
See WebFluxConfigurer.extendMessageWriters(List) for adding writers
in addition to the default ones.
configureMessageWriters in interface WebFluxConfigurerwriters - a empty list to add message writers topublic void extendMessageWriters(java.util.List<HttpMessageWriter<?>> writers)
WebFluxConfigurerWebFluxConfigurer.configureMessageWriters(List) that allows
modifying the message writers to use after default ones have been added.extendMessageWriters in interface WebFluxConfigurerpublic void configureViewResolvers(ViewResolverRegistry registry)
WebFluxConfigurerView 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.configureViewResolvers in interface WebFluxConfigurerViewResolverRegistryprivate <T> java.util.Optional<T> createSingleBean(java.util.function.Function<WebFluxConfigurer,java.util.Optional<T>> factory, java.lang.Class<T> beanType)