See: Description
| Interface | Description |
|---|---|
| BodyExtractor<T> |
A function that can extract data from a
Request body. |
| BodyInserter<T> |
A component that can insert data into a
Response body. |
| FilterFunction<T,R> |
Represents a function that filters a handler function.
|
| HandlerFunction<T> |
Represents a function that handles a request.
|
| Rendering |
Represents a template rendering, based on a
String name and a model Map. |
| Request |
Represents an HTTP request, as handled by a
HandlerFunction. |
| Request.Headers |
Represents the headers of the HTTP request.
|
| RequestPredicate |
Represents a function that evaluates on a given
Request. |
| Response<T> |
Represents a typed HTTP response, as returned by a handler function or
filter function.
|
| Response.BodyBuilder |
Defines a builder that adds a body to the response.
|
| Response.HeadersBuilder<B extends Response.HeadersBuilder<B>> |
Defines a builder that adds headers to the response.
|
| RouterFunction<T> |
Represents a function that routes to a handler function.
|
| StrategiesSupplier |
Defines the strategies to be used for processing
HandlerFunctions. |
| StrategiesSupplier.Builder |
A mutable builder for a
StrategiesSupplier. |
| Class | Description |
|---|---|
| BodyExtractors |
Implementations of
BodyExtractor that read various bodies, such a reactive streams. |
| BodyInserters |
Implementations of
BodyInserter that write various bodies, such a reactive streams,
server-sent events, resources, etc. |
| RequestPredicates |
Implementations of
RequestPredicate that implement various useful request matching operations, such as
matching based on path, HTTP method, etc. |
| RouterFunctions |
Central entry point to Spring's functional web framework.
Exposes routing functionality, such as to
create a
RouterFunction given a
RequestPredicate and HandlerFunction, and to do further
subrouting on an existing routing
function. |