Migrate to servlet binder for web features
This commit is contained in:
@@ -41,12 +41,11 @@ JMS.
|
||||
|
||||
The `@Beans` can be `Function`, `Consumer` or `Supplier` (all from
|
||||
`java.util`), and their parametric types can be String or POJO. A
|
||||
`Function` is exposed as an HTTP POST if `spring-cloud-function-web`
|
||||
is on the classpath, and as a Spring Cloud Stream `Processor` if
|
||||
`spring-cloud-function-stream` is on the classpath and a
|
||||
`spring.cloud.function.stream.endpoint` property is configured in the Spring
|
||||
environment. A `Consumer` is also exposed as an HTTP POST, or as a Stream
|
||||
`Sink`. A `Supplier` translates to an HTTP GET, or a Stream `Source`.
|
||||
`Function` is exposed as a Spring Cloud Stream `Processor` if
|
||||
`spring-cloud-function-stream` is on the classpath.
|
||||
A `Consumer` is also exposed as a Stream
|
||||
`Sink` and a `Supplier` translates to a Stream `Source`.
|
||||
HTTP endpoints are exposed if the Stream binder is `spring-cloud-stream-binder-servlet`.
|
||||
|
||||
Functions can be of `Flux<String>` or `Flux<Pojo>` and Spring Cloud
|
||||
Function takes care of converting the data to and from the desired
|
||||
|
||||
Reference in New Issue
Block a user