Sync docs from master to gh-pages

multi/multi__building_and_running_a_function.html

@@ -6,14 +6,17 @@ or a Stream processor, for instance with RabbitMQ, Apache Kafka or
 JMS.</p><p>The <code class="literal">@Beans</code> can be <code class="literal">Function</code>, <code class="literal">Consumer</code> or <code class="literal">Supplier</code> (all from
 <code class="literal">java.util</code>), and their parametric types can be String or POJO. A
 <code class="literal">Function</code> is exposed as a Spring Cloud Stream <code class="literal">Processor</code> if
-<code class="literal">spring-cloud-function-stream</code> is on the classpath.
-A <code class="literal">Consumer</code> is also exposed as a Stream
-<code class="literal">Sink</code> and a <code class="literal">Supplier</code> translates to a Stream <code class="literal">Source</code>.
-HTTP endpoints are exposed if the Stream binder is <code class="literal">spring-cloud-stream-binder-servlet</code>.</p><p>Functions can be of <code class="literal">Flux&lt;String&gt;</code> or <code class="literal">Flux&lt;Pojo&gt;</code> 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 <code class="literal">Flux&lt;Message&lt;Pojo&gt;&gt;</code> and maybe plain
-<code class="literal">Pojo</code> types (Fluxes implied and implemented by the framework).</p><p>Functions can be grouped together in a single application, or deployed
+<code class="literal">spring-cloud-function-stream</code> is on the classpath.  A <code class="literal">Consumer</code> is
+also exposed as a Stream <code class="literal">Sink</code>, and a <code class="literal">Supplier</code> translates to a
+Stream <code class="literal">Source</code>.</p><p>Functions can also be of <code class="literal">Flux&lt;String&gt;</code> or <code class="literal">Flux&lt;Pojo&gt;</code> 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 <code class="literal">Message&lt;Pojo&gt;</code> 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 <code class="literal">Map</code>, 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.</p><p>Functions can be grouped together in a single application, or deployed
 one-per-jar. It&#8217;s up to the developer to choose. An app with multiple
 functions can be deployed multiple times in different "personalities",
 exposing different functions over different physical transports.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="multi__getting_started.html">Prev</a>&nbsp;</td><td width="20%" align="center">&nbsp;</td><td width="40%" align="right">&nbsp;<a accesskey="n" href="multi__function_catalog_and_flexible_function_signatures.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.&nbsp;Getting Started&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="multi_spring-cloud-function.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;4.&nbsp;Function Catalog and Flexible Function Signatures</td></tr></table></div></body></html>

single/spring-cloud-function.html

@@ -36,14 +36,17 @@ or a Stream processor, for instance with RabbitMQ, Apache Kafka or
 JMS.</p><p>The <code class="literal">@Beans</code> can be <code class="literal">Function</code>, <code class="literal">Consumer</code> or <code class="literal">Supplier</code> (all from
 <code class="literal">java.util</code>), and their parametric types can be String or POJO. A
 <code class="literal">Function</code> is exposed as a Spring Cloud Stream <code class="literal">Processor</code> if
-<code class="literal">spring-cloud-function-stream</code> is on the classpath.
-A <code class="literal">Consumer</code> is also exposed as a Stream
-<code class="literal">Sink</code> and a <code class="literal">Supplier</code> translates to a Stream <code class="literal">Source</code>.
-HTTP endpoints are exposed if the Stream binder is <code class="literal">spring-cloud-stream-binder-servlet</code>.</p><p>Functions can be of <code class="literal">Flux&lt;String&gt;</code> or <code class="literal">Flux&lt;Pojo&gt;</code> 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 <code class="literal">Flux&lt;Message&lt;Pojo&gt;&gt;</code> and maybe plain
-<code class="literal">Pojo</code> types (Fluxes implied and implemented by the framework).</p><p>Functions can be grouped together in a single application, or deployed
+<code class="literal">spring-cloud-function-stream</code> is on the classpath.  A <code class="literal">Consumer</code> is
+also exposed as a Stream <code class="literal">Sink</code>, and a <code class="literal">Supplier</code> translates to a
+Stream <code class="literal">Source</code>.</p><p>Functions can also be of <code class="literal">Flux&lt;String&gt;</code> or <code class="literal">Flux&lt;Pojo&gt;</code> 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 <code class="literal">Message&lt;Pojo&gt;</code> 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 <code class="literal">Map</code>, 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.</p><p>Functions can be grouped together in a single application, or deployed
 one-per-jar. It&#8217;s up to the developer to choose. An app with multiple
 functions can be deployed multiple times in different "personalities",
 exposing different functions over different physical transports.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="_function_catalog_and_flexible_function_signatures" href="#_function_catalog_and_flexible_function_signatures"></a>4.&nbsp;Function Catalog and Flexible Function Signatures</h1></div></div></div><p>One of the main features of Spring Cloud Function is to adapt and support a range of type signatures for user-defined functions,

spring-cloud-function.xml

@@ -103,15 +103,18 @@ JMS.</simpara>
 <simpara>The <literal>@Beans</literal> can be <literal>Function</literal>, <literal>Consumer</literal> or <literal>Supplier</literal> (all from
 <literal>java.util</literal>), and their parametric types can be String or POJO. A
 <literal>Function</literal> is exposed as a Spring Cloud Stream <literal>Processor</literal> if
-<literal>spring-cloud-function-stream</literal> is on the classpath.
-A <literal>Consumer</literal> is also exposed as a Stream
-<literal>Sink</literal> and a <literal>Supplier</literal> translates to a Stream <literal>Source</literal>.
-HTTP endpoints are exposed if the Stream binder is <literal>spring-cloud-stream-binder-servlet</literal>.</simpara>
-<simpara>Functions can be of <literal>Flux&lt;String&gt;</literal> or <literal>Flux&lt;Pojo&gt;</literal> 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 <literal>Flux&lt;Message&lt;Pojo&gt;&gt;</literal> and maybe plain
-<literal>Pojo</literal> types (Fluxes implied and implemented by the framework).</simpara>
+<literal>spring-cloud-function-stream</literal> is on the classpath.  A <literal>Consumer</literal> is
+also exposed as a Stream <literal>Sink</literal>, and a <literal>Supplier</literal> translates to a
+Stream <literal>Source</literal>.</simpara>
+<simpara>Functions can also be of <literal>Flux&lt;String&gt;</literal> or <literal>Flux&lt;Pojo&gt;</literal> 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 <literal>Message&lt;Pojo&gt;</literal> 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 <literal>Map</literal>, 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.</simpara>
 <simpara>Functions can be grouped together in a single application, or deployed
 one-per-jar. It&#8217;s up to the developer to choose. An app with multiple
 functions can be deployed multiple times in different "personalities",