SpringCloud/spring-cloud-function
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Tidy up TBD in docs

Browse Source
This commit is contained in:
Dave Syer
2018-10-29 08:59:45 +00:00
parent 9cf723949b
commit a03e34b6ee
1 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/src/main/asciidoc/getting-started.adoc
View File

@@ -42,16 +42,19 @@ JMS.
The `@Beans` can be `Function`, `Consumer` or `Supplier` (all from The `@Beans` can be `Function`, `Consumer` or `Supplier` (all from
`java.util`), and their parametric types can be String or POJO. A `java.util`), and their parametric types can be String or POJO. A
`Function` is exposed as a Spring Cloud Stream `Processor` if `Function` is exposed as a Spring Cloud Stream `Processor` if
`spring-cloud-function-stream` is on the classpath. `spring-cloud-function-stream` is on the classpath. A `Consumer` is
A `Consumer` is also exposed as a Stream also exposed as a Stream `Sink`, and a `Supplier` translates to a
`Sink` and a `Supplier` translates to a Stream `Source`. 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 Functions can also be of `Flux<String>` or `Flux<Pojo>` and Spring
Function takes care of converting the data to and from the desired Cloud Function takes care of converting the data to and from the
types, as long as it comes in as plain text or (in the case of the desired types, as long as it comes in as plain text or (in the case of
POJO) JSON. TBD: support for `Flux<Message<Pojo>>` and maybe plain the POJO) JSON. There is also support for `Message<Pojo>` where the
`Pojo` types (Fluxes implied and implemented by the framework). message headers are copied from the incoming event, depending on the
adapter. The web adapter also supports conversion from form-encoded
data to a `Map`, and if you are using the function with Spring Cloud
Stream then all the conversion and coercion features for message
payloads will be applicable as well.
Functions can be grouped together in a single application, or deployed Functions can be grouped together in a single application, or deployed
one-per-jar. It's up to the developer to choose. An app with multiple one-per-jar. It's up to the developer to choose. An app with multiple