diff --git a/aws-intro.html b/aws-intro.html index 4238e4f37..91086e7d7 100644 --- a/aws-intro.html +++ b/aws-intro.html @@ -90,6 +90,11 @@ $(addBlockSwitches);
@@ -163,6 +168,31 @@ The AWS sample app is written in the "functional" style (as anApplication
+
+Type Conversion
+
+
+Spring Cloud Function will attempt to transparently handle type conversion between the raw
+input stream and types declared by your function.
+
+
+For example, if your function signature is as such Function<Foo, Bar> we will attempt to convert
+incoming stream event to an instance of Foo.
+
+
+In the event type is not known or can not be determined (e.g., Function<?, ?>) we will attempt to
+convert an incoming stream event to a generic Map.
+
+
+Raw Input
+
+There are times when you may want to have access to a raw input. In this case all you need is to declare your
+function signature to accept InputStream. For example, Function<InputStream, ?>. In this case
+we will not attempt any conversion and will pass the raw input directly to a function.
+
+
+
+
diff --git a/aws-readme.html b/aws-readme.html
index 929fd46e9..967d27ce7 100644
--- a/aws-readme.html
+++ b/aws-readme.html
@@ -90,6 +90,11 @@ $(addBlockSwitches);
@@ -166,6 +171,31 @@ The AWS sample app is written in the "functional" style (as an Application
+
+Type Conversion
+
+
+Spring Cloud Function will attempt to transparently handle type conversion between the raw
+input stream and types declared by your function.
+
+
+For example, if your function signature is as such Function<Foo, Bar> we will attempt to convert
+incoming stream event to an instance of Foo.
+
+
+In the event type is not known or can not be determined (e.g., Function<?, ?>) we will attempt to
+convert an incoming stream event to a generic Map.
+
+
+Raw Input
+
+There are times when you may want to have access to a raw input. In this case all you need is to declare your
+function signature to accept InputStream. For example, Function<InputStream, ?>. In this case
+we will not attempt any conversion and will pass the raw input directly to a function.
+
+
+
+
diff --git a/aws.html b/aws.html
index ec84f1f3d..2d7f8e993 100644
--- a/aws.html
+++ b/aws.html
@@ -91,6 +91,11 @@ $(addBlockSwitches);
Introduction
Notes on JAR Layout
Upload
+Type Conversion
+
+- Raw Input
+
+
Functional Bean Definitions
Platfom Specific Features
@@ -108,7 +113,7 @@ $(addBlockSwitches);
2.1.0.BUILD-SNAPSHOT
-https://cloud.spring.io/spring-cloud-function/home.html
+https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html
The AWS adapter takes a Spring Cloud Function app and converts it to a form that can run in AWS Lambda.
@@ -186,6 +191,31 @@ The AWS sample app is written in the "functional" style (as an Application
+Type Conversion
+
+
+Spring Cloud Function will attempt to transparently handle type conversion between the raw
+input stream and types declared by your function.
+
+
+For example, if your function signature is as such Function<Foo, Bar> we will attempt to convert
+incoming stream event to an instance of Foo.
+
+
+In the event type is not known or can not be determined (e.g., Function<?, ?>) we will attempt to
+convert an incoming stream event to a generic Map.
+
+
+Raw Input
+
+There are times when you may want to have access to a raw input. In this case all you need is to declare your
+function signature to accept InputStream. For example, Function<InputStream, ?>. In this case
+we will not attempt any conversion and will pass the raw input directly to a function.
+
+
+
+
+
Functional Bean Definitions
diff --git a/azure.html b/azure.html
index a0d7e697e..c9517b20c 100644
--- a/azure.html
+++ b/azure.html
@@ -102,7 +102,7 @@ $(addBlockSwitches);
2.1.0.BUILD-SNAPSHOT
-https://cloud.spring.io/spring-cloud-function/home.html
+https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html
The Azure adapter bootstraps a Spring Cloud Function context and channels function calls from the Azure framework into the user functions, using Spring Boot configuration where necessary. Azure Functions has quite a unique, but invasive programming model, involving annotations in user code that are specific to the platform. The easiest way to use it with Spring Cloud is to extend a base class and write a method in it with the @FunctionName annotation which delegates to a base class method.
diff --git a/openwhisk.html b/openwhisk.html
index 4d3b59478..53d0b7816 100644
--- a/openwhisk.html
+++ b/openwhisk.html
@@ -99,7 +99,7 @@ $(addBlockSwitches);
2.1.0.BUILD-SNAPSHOT
-https://cloud.spring.io/spring-cloud-function/home.html
+https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html
The OpenWhisk adapter is in the form of an executable jar that can be used in a a docker image to be deployed to Openwhisk. The platform works in request-response mode, listening on port 8080 on a specific endpoint, so the adapter is a simple Spring MVC application.
diff --git a/spring-cloud-function.html b/spring-cloud-function.html
index ad60cee9d..0783befa9 100644
--- a/spring-cloud-function.html
+++ b/spring-cloud-function.html
@@ -124,7 +124,7 @@ $(addBlockSwitches);