From b23a647aa4ac429126709c2aeddf0243d2b2d3e2 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Fri, 16 Nov 2018 15:20:37 +0000 Subject: [PATCH] Bumping versions --- README.adoc | 21 +++++++++---------- .../README.adoc | 2 +- 2 files changed, 11 insertions(+), 12 deletions(-) diff --git a/README.adoc b/README.adoc index db227d7fe..45bc6da76 100644 --- a/README.adoc +++ b/README.adoc @@ -100,18 +100,17 @@ or a Stream processor, for instance with RabbitMQ, Apache Kafka or 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 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`. +`java.util`), and their parametric types can be String or POJO. -Functions can be of `Flux` or `Flux` and Spring Cloud -Function takes care of converting the data to and from the desired -types, as long as it comes in as plain text or (in the case of the -POJO) JSON. TBD: support for `Flux>` and maybe plain -`Pojo` types (Fluxes implied and implemented by the framework). +Functions can also be of `Flux` or `Flux` and Spring +Cloud Function takes care of converting the data to and from the +desired types, as long as it comes in as plain text or (in the case of +the POJO) JSON. There is also support for `Message` where the +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 one-per-jar. It's up to the developer to choose. An app with multiple diff --git a/spring-cloud-function-adapters/spring-cloud-function-adapter-azure/README.adoc b/spring-cloud-function-adapters/spring-cloud-function-adapter-azure/README.adoc index 3d4ddc8c9..bb0562ae9 100644 --- a/spring-cloud-function-adapters/spring-cloud-function-adapter-azure/README.adoc +++ b/spring-cloud-function-adapters/spring-cloud-function-adapter-azure/README.adoc @@ -64,7 +64,7 @@ The input type for the function in the Azure sample is a Foo with a single prope } ---- -NOTE: The Azure sample app is written in the "non-functional" style (using `@Bean`). The functional style (with just `Function` or `ApplicationContextInitializer`) is is much faster on startup in Azure than the traditional `@Bean` style, so if you don't need `@Beans` (or `@EnableAutoConfiguration`) it's a good choice. Warm starts are not affected. +NOTE: The Azure sample app is written in the "non-functional" style (using `@Bean`). The functional style (with just `Function` or `ApplicationContextInitializer`) is much faster on startup in Azure than the traditional `@Bean` style, so if you don't need `@Beans` (or `@EnableAutoConfiguration`) it's a good choice. Warm starts are not affected. == Sample Function