Sync docs from master to gh-pages
This commit is contained in:
buildmaster
@@ -90,6 +90,11 @@ $(addBlockSwitches);
|
||||
<ul class="sectlevel1">
|
||||
<li><a href="#_notes_on_jar_layout">Notes on JAR Layout</a></li>
|
||||
<li><a href="#_upload">Upload</a></li>
|
||||
<li><a href="#_type_conversion">Type Conversion</a>
|
||||
<ul class="sectlevel3">
|
||||
<li><a href="#_raw_input">Raw Input</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
@@ -163,6 +168,31 @@ The AWS sample app is written in the "functional" style (as an <code>Application
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
<h2 id="_type_conversion"><a class="link" href="#_type_conversion">Type Conversion</a></h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph">
|
||||
<p>Spring Cloud Function will attempt to transparently handle type conversion between the raw
|
||||
input stream and types declared by your function.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>For example, if your function signature is as such <code>Function<Foo, Bar></code> we will attempt to convert
|
||||
incoming stream event to an instance of <code>Foo</code>.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In the event type is not known or can not be determined (e.g., <code>Function<?, ?></code>) we will attempt to
|
||||
convert an incoming stream event to a generic <code>Map</code>.</p>
|
||||
</div>
|
||||
<div class="sect3">
|
||||
<h4 id="_raw_input"><a class="link" href="#_raw_input">Raw Input</a></h4>
|
||||
<div class="paragraph">
|
||||
<p>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 <code>InputStream</code>. For example, <code>Function<InputStream, ?></code>. In this case
|
||||
we will not attempt any conversion and will pass the raw input directly to a function.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<script type="text/javascript" src="js/tocbot/tocbot.min.js"></script>
|
||||
<script type="text/javascript" src="js/toc.js"></script>
|
||||
|
||||
@@ -90,6 +90,11 @@ $(addBlockSwitches);
|
||||
<ul class="sectlevel1">
|
||||
<li><a href="#_notes_on_jar_layout">Notes on JAR Layout</a></li>
|
||||
<li><a href="#_upload">Upload</a></li>
|
||||
<li><a href="#_type_conversion">Type Conversion</a>
|
||||
<ul class="sectlevel3">
|
||||
<li><a href="#_raw_input">Raw Input</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
@@ -166,6 +171,31 @@ The AWS sample app is written in the "functional" style (as an <code>Application
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
<h2 id="_type_conversion"><a class="link" href="#_type_conversion">Type Conversion</a></h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph">
|
||||
<p>Spring Cloud Function will attempt to transparently handle type conversion between the raw
|
||||
input stream and types declared by your function.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>For example, if your function signature is as such <code>Function<Foo, Bar></code> we will attempt to convert
|
||||
incoming stream event to an instance of <code>Foo</code>.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In the event type is not known or can not be determined (e.g., <code>Function<?, ?></code>) we will attempt to
|
||||
convert an incoming stream event to a generic <code>Map</code>.</p>
|
||||
</div>
|
||||
<div class="sect3">
|
||||
<h4 id="_raw_input"><a class="link" href="#_raw_input">Raw Input</a></h4>
|
||||
<div class="paragraph">
|
||||
<p>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 <code>InputStream</code>. For example, <code>Function<InputStream, ?></code>. In this case
|
||||
we will not attempt any conversion and will pass the raw input directly to a function.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<script type="text/javascript" src="js/tocbot/tocbot.min.js"></script>
|
||||
<script type="text/javascript" src="js/toc.js"></script>
|
||||
|
||||
32
aws.html
32
aws.html
@@ -91,6 +91,11 @@ $(addBlockSwitches);
|
||||
<li><a href="#_introduction">Introduction</a></li>
|
||||
<li><a href="#_notes_on_jar_layout">Notes on JAR Layout</a></li>
|
||||
<li><a href="#_upload">Upload</a></li>
|
||||
<li><a href="#_type_conversion">Type Conversion</a>
|
||||
<ul class="sectlevel3">
|
||||
<li><a href="#_raw_input">Raw Input</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#_functional_bean_definitions">Functional Bean Definitions</a></li>
|
||||
<li><a href="#_platfom_specific_features">Platfom Specific Features</a>
|
||||
<ul class="sectlevel2">
|
||||
@@ -108,7 +113,7 @@ $(addBlockSwitches);
|
||||
<p><strong>2.1.0.BUILD-SNAPSHOT</strong></p>
|
||||
</div>
|
||||
<div id="index-link" class="paragraph">
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-function/home.html" class="bare">https://cloud.spring.io/spring-cloud-function/home.html</a></p>
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html" class="bare">https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html</a></p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>The <a href="https://aws.amazon.com/">AWS</a> adapter takes a Spring Cloud Function app and converts it to a form that can run in AWS Lambda.</p>
|
||||
@@ -186,6 +191,31 @@ The AWS sample app is written in the "functional" style (as an <code>Application
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
<h2 id="_type_conversion"><a class="link" href="#_type_conversion">Type Conversion</a></h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph">
|
||||
<p>Spring Cloud Function will attempt to transparently handle type conversion between the raw
|
||||
input stream and types declared by your function.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>For example, if your function signature is as such <code>Function<Foo, Bar></code> we will attempt to convert
|
||||
incoming stream event to an instance of <code>Foo</code>.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>In the event type is not known or can not be determined (e.g., <code>Function<?, ?></code>) we will attempt to
|
||||
convert an incoming stream event to a generic <code>Map</code>.</p>
|
||||
</div>
|
||||
<div class="sect3">
|
||||
<h4 id="_raw_input"><a class="link" href="#_raw_input">Raw Input</a></h4>
|
||||
<div class="paragraph">
|
||||
<p>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 <code>InputStream</code>. For example, <code>Function<InputStream, ?></code>. In this case
|
||||
we will not attempt any conversion and will pass the raw input directly to a function.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
<h2 id="_functional_bean_definitions"><a class="link" href="#_functional_bean_definitions">Functional Bean Definitions</a></h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph">
|
||||
|
||||
@@ -102,7 +102,7 @@ $(addBlockSwitches);
|
||||
<p><strong>2.1.0.BUILD-SNAPSHOT</strong></p>
|
||||
</div>
|
||||
<div id="index-link" class="paragraph">
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-function/home.html" class="bare">https://cloud.spring.io/spring-cloud-function/home.html</a></p>
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html" class="bare">https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html</a></p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>The <a href="https://azure.microsoft.com">Azure</a> 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 <code>@FunctionName</code> annotation which delegates to a base class method.</p>
|
||||
|
||||
@@ -99,7 +99,7 @@ $(addBlockSwitches);
|
||||
<p><strong>2.1.0.BUILD-SNAPSHOT</strong></p>
|
||||
</div>
|
||||
<div id="index-link" class="paragraph">
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-function/home.html" class="bare">https://cloud.spring.io/spring-cloud-function/home.html</a></p>
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html" class="bare">https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html</a></p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>The <a href="https://openwhisk.apache.org/">OpenWhisk</a> 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.</p>
|
||||
|
||||
@@ -124,7 +124,7 @@ $(addBlockSwitches);
|
||||
</div>
|
||||
<hr>
|
||||
<div id="index-link" class="paragraph">
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-function/home.html" class="bare">https://cloud.spring.io/spring-cloud-function/home.html</a></p>
|
||||
<p><a href="https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html" class="bare">https://cloud.spring.io/spring-cloud-static/spring-cloud-function/2.1.0.RC1/home.html</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user