From 2c5e71e25753eb4615ecef9517b872722e09f117 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Mon, 29 Oct 2018 15:06:20 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__building_and_running_a_function.html | 6 +----- single/spring-cloud-function.html | 6 +----- spring-cloud-function.xml | 6 +----- 3 files changed, 3 insertions(+), 15 deletions(-) diff --git a/multi/multi__building_and_running_a_function.html b/multi/multi__building_and_running_a_function.html index 9afad9ea3..3e45435e8 100644 --- a/multi/multi__building_and_running_a_function.html +++ b/multi/multi__building_and_running_a_function.html @@ -4,11 +4,7 @@ decorated at runtime by Spring Cloud Function to be an HTTP endpoint, 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.

Functions can also be of Flux<String> or Flux<Pojo> and Spring +java.util), and their parametric types can be String or POJO.

Functions can also be of Flux<String> or Flux<Pojo> 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<Pojo> where the diff --git a/single/spring-cloud-function.html b/single/spring-cloud-function.html index b371eee00..6f9d5515b 100644 --- a/single/spring-cloud-function.html +++ b/single/spring-cloud-function.html @@ -34,11 +34,7 @@ string like that.)

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.

Functions can also be of Flux<String> or Flux<Pojo> and Spring +java.util), and their parametric types can be String or POJO.

Functions can also be of Flux<String> or Flux<Pojo> 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<Pojo> where the diff --git a/spring-cloud-function.xml b/spring-cloud-function.xml index 3754716bb..865de4970 100644 --- a/spring-cloud-function.xml +++ b/spring-cloud-function.xml @@ -101,11 +101,7 @@ decorated at runtime by Spring Cloud Function to be an HTTP endpoint, 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. +java.util), and their parametric types can be String or POJO. Functions can also be of Flux<String> or Flux<Pojo> 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