This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 9898182 Automatic website deployment
9898182 is described below
commit 989818265611eeb2359253e452d91dd9f25b4ee2
Author: jenkins <[email protected]>
AuthorDate: Tue Feb 12 10:50:38 2019 +0000
Automatic website deployment
---
documentation/bundles/sling-pipes/bindings.html | 6 ++++--
documentation/bundles/sling-pipes/writers.html | 6 +++---
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/documentation/bundles/sling-pipes/bindings.html
b/documentation/bundles/sling-pipes/bindings.html
index ce4c769..fa0e3a4 100644
--- a/documentation/bundles/sling-pipes/bindings.html
+++ b/documentation/bundles/sling-pipes/bindings.html
@@ -112,7 +112,8 @@
}
</code></pre>
<h2><a href="#additional-bindings" name="additional-bindings">additional
bindings</a></h2>
-<p>additional bindings is a <a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#jcr-persistence-of-a-pipe.html">node
you add to your pipe definition</a>, that sets bindings for the whole pipe
execution. You can also add some through <a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#pipe-builder-api">pipe
builder api</a> with a map of bindings</p>
+<p><code>additionalBindings</code> is a <a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#jcr-persistence-of-a-pipe.html">node
you add to any pipe definition</a>, that sets its properties as bindings for
this pipe's context execution. you can also add
<code>additionalBindings/providers</code> children, that should be read-only
pipes that will get executed before this pipe execution, to provide dynamic
bindings. </p>
+<p>You can also add some through <a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#pipe-builder-api">pipe
builder api</a> with a map of bindings</p>
<pre><code> .run(bindings)
</code></pre>
<p>or with a set of key / value pairs</p>
@@ -121,13 +122,14 @@
<p><a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#http-api">http
api</a> for this is a binding parameter</p>
<pre><code> -F bindings='{"env":"prod"}'
</code></pre>
+<p>In case a pipe needs a more dynamic binding, you can use another pipe as
binding provider, </p>
<h2><a href="#additional-scripts" name="additional-scripts">additional
scripts</a></h2>
<p>some times you want heavy js logic in your expression instantiation. In
that case, you need to store your javascript somewhere in the JCR, and mentions
the path in the <a
href="/documentation/bundles/sling-pipes/execution-monitoring.html#jcr-persistence-of-a-pipe.html">additionalScripts
MV property</a></p>
<h2><a href="#bindings-forward" name="bindings-forward">bindings
forward</a></h2>
<p>in case a pipe references, or contain another pipe, same binding space will
be used</p></section></div></div>
<footer class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Mon Oct 8 17:09:17 2018 +0200</span>
+ Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Tue Feb 12 11:46:55 2019 +0100</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and
the Apache Sling project logo are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their
respective owners.
</p><p>
diff --git a/documentation/bundles/sling-pipes/writers.html
b/documentation/bundles/sling-pipes/writers.html
index 11854fa..a244e27 100644
--- a/documentation/bundles/sling-pipes/writers.html
+++ b/documentation/bundles/sling-pipes/writers.html
@@ -88,8 +88,8 @@
<pre><code> .echo('/content/foo')
.write('foo1','bar1','foo2','bar2')
</code></pre>
-<p>will write <code>@foo1=bar1</code> and <code>@foo2=bar2</code> in
<code>/content/foo</code>. For more complicated cases where you need a
structure to be written, just use a JCR / Resource explorer to edit the
persistence of the pipe, and create the given structured under conf.</p>
-<p>Note that using <code>expr</code> you need configuration node <em>not</em>
to be here, and {{write}} shortcut creates one systematically. So if you want
to use pipe builder and that, you'd need something like</p>
+<p>will write <code>@foo1=bar1</code> and <code>@foo2=bar2</code> in
<code>/content/foo</code>. For more complicated cases where you need a
structure to be written, just use a JCR / Resource explorer to edit the
persistence of the pipe, and create the given structured under conf. Note that
you can use expressions in that node tree, and specifically, for a node name,
parent of a tree you want to be conditionally written, use
<code>$if${...}nodename</code> syntax, that will basically only [...]
+<p>Note that using <code>expr</code> you need configuration node <em>not</em>
to be here, and <code>write</code> shortcut creates one systematically. So if
you want to use pipe builder and that, you'd need something like</p>
<pre><code> .echo('/content/destination')
.pipe("slingPipes/write").expr("/content/source")
</code></pre>
@@ -176,7 +176,7 @@
</code></pre></section></div></div>
<footer class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">dichaudh</span> on
<span class="comment">Fri Oct 19 18:44:17 2018 +0530</span>
+ Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Tue Feb 12 11:46:55 2019 +0100</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and
the Apache Sling project logo are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their
respective owners.
</p><p>
