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 c75709a Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/36/
c75709a is described below
commit c75709a77714412db31d72c5571d696da5174b59
Author: jenkins <[email protected]>
AuthorDate: Wed Sep 30 14:16:55 2020 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/36/
---
documentation/bundles/sling-pipes.html | 5 ++++-
documentation/bundles/sling-pipes/bindings.html | 5 +++--
documentation/bundles/sling-pipes/execution-monitoring.html | 5 ++++-
downloads.html | 6 +++---
4 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/documentation/bundles/sling-pipes.html
b/documentation/bundles/sling-pipes.html
index c5f5baf..80da952 100644
--- a/documentation/bundles/sling-pipes.html
+++ b/documentation/bundles/sling-pipes.html
@@ -124,6 +124,9 @@
<pre><code>
plumber.newPipe(resolver).$("foo/bar").write("id",3).build("/etc/demo")
</code></pre>
<p>this is enough to persist a pipe in <code>/etc/demo</code> that is
executable as http, java, groovy console script, or JMX. You can monitor it
with JMX, logs, http, you'll have dry run possibility of that execution for
example, or asynchronous execution. You could also use a pipe to create a
java-free json or csv servlet, or a list component whose list possibilities are
pipes accessed through the <code>PipeModel</code></p>
+<p>or, if you are testing things from the command line, using a curl script
named "pipe"</p>
+<pre><code> pipe "$ foo/bar | write id 3"
+</code></pre>
<p>you can check some introductions at different adaptTo presentations:</p>
<h2><a href="#adaptto-introductions" id="adaptto-introductions">AdaptTo
introductions</a></h2>
<p>some presentations were made at the adaptTo conference, last two were:</p>
@@ -169,7 +172,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Stefan
Popescu</span> on <span class="comment">Mon Oct 8 19:28:20 2018 +0300</span>
+ Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Wed Sep 30 16:12:41 2020 +0200</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/bindings.html
b/documentation/bundles/sling-pipes/bindings.html
index 06f292c..13d3497 100644
--- a/documentation/bundles/sling-pipes/bindings.html
+++ b/documentation/bundles/sling-pipes/bindings.html
@@ -118,7 +118,8 @@
</li>
</ul>
</nav><script src='/res/jquery-3.2.1.min.js'
type='text/javascript'></script><script src='/res/tocjs-1-1-2.js'
type='text/javascript'></script><script
type='text/javascript'>$(document).ready(function() {
$('#generatedToC').toc({'selector':'h1[class!=title],h2,h3','ulClass':'menu-list'});
} );</script><div class="content is-marginless">
-<div class="row"><div><section><p>in order to make things interesting, most of
the configuration strings are javascript template strings, hence valid js
expressions reusing bindings (from configuration, or other pipes).</p>
+<div class="row"><div><section><p>in order to make things interesting, most of
the configuration strings are expressions strings, hence valid JEXL expressions
reusing bindings (from configuration, or other pipes). They work the same as JS
expressions, except you can't add full JS files.</p>
+<p>You can also set whatever scripting engine you want per pipe (including
nashorn, rhino, groovy, ...)</p>
<h2><a href="#configuration-expression"
id="configuration-expression">configuration expression</a></h2>
<p>an expression (path, expr, or property name or value in conf tree) can be
either a pure string, like <code>/content/foo/bar</code> or
<code>nt:unstructured[title=foo]</code>. But using <em>static</em> expressions
like this is rather limited for most of the cases, hence usage of ECMA
expressions like <code>/content/${one.value}/bar</code> or more sophisticated
using functions
<code>nt:unstructured[title=${getValue(currentField)}]</code></p>
<p>In case the expression has an error (bad expression, or undefined variable
we'll name <code>bindings</code>) non instanciated expression will be
outputed</p>
@@ -176,7 +177,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Tue Feb 12 11:46:55 2019 +0100</span>
+ Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Wed Sep 30 16:12:41 2020 +0200</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/execution-monitoring.html
b/documentation/bundles/sling-pipes/execution-monitoring.html
index 331daa2..326aeff 100644
--- a/documentation/bundles/sling-pipes/execution-monitoring.html
+++ b/documentation/bundles/sling-pipes/execution-monitoring.html
@@ -204,7 +204,10 @@
<p>when installing pipes bundle, <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-gogo.html";>apache
felix gogo</a> commands are exposed to the console that allow you to - build
(pipe:build or just build if no other command) - run (pipe:run or just run if
no other command) - execute (pipe:execute or just execute if no other command)
- and print help on how to use the above</p>
<p>the pipe is here represented as <code>/</code> character as <code>|</code>
is already used by gogo console, an heavy usage of the gogo console is made in
the <a
href="http://localhost:8820/documentation/bundles/sling-pipes.html#adaptto-introductions";>main
page videos</a>, or you can direcly check in there for sample gogo commands
for <a href="https://github.com/npeltier/99-bottles-of-beers-with-sling";>99
bottles of beer</a> sample.</p>
<h3><a href="#http-api" id="http-api">HTTP API</a></h3>
+<h4><a href="#build-run-pipe-from-command-line"
id="build-run-pipe-from-command-line">Build & Run Pipe from command
line</a></h4>
+<p>now you can run same commands as gogo commands directly from your command
line tool, using either pipe_cmd parameter and <code>echo /content | write
child/foo=bar</code> value. Either you can use <code>pipe_cmdfile</code> with
several pipes in there. In that case <code>cmd_line_N</code> where
<code>N</code> is the nth effective pipe of your script is a binding added with
the corresponding pipe path (useful for using reference pipes).</p>
<h4><a href="#pipe-http-request-bits" id="pipe-http-request-bits">Pipe HTTP
Request bits</a></h4>
+<p>If the pipe already exists in your repository you can run it following up
below constraints</p>
<table>
<thead>
<tr><th> request bit </th><th> Explanation </th></tr>
@@ -269,7 +272,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<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">Wed Sep 30 16:12:41 2020 +0200</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/downloads.html b/downloads.html
index be366da..d3c3393 100644
--- a/downloads.html
+++ b/downloads.html
@@ -581,9 +581,9 @@
</td></tr><tr><td>Performance Test Utilities</td><td>1.0.2</td><td><a
href="https://github.com/apache/sling-org-apache-sling-performance";>GitHub</a>
</td><td><a
href="[preferred]sling/org.apache.sling.performance.base-1.0.2.jar">Bundle</a>
(<a
href="https://downloads.apache.org/sling/org.apache.sling.performance.base-1.0.2.jar.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.performance.base-1.0.2.jar.sha1";>sha1</a>)
</td><td><a
href="[preferred]sling/org.apache.sling.performance.base-1.0.2-source-release.zip">Source
ZIP</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.performance.base-1.0.2-source-release.zip.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.performance.base-1.0.2-source-release.zip.sha1";>sha1</a>)
-
</td></tr><tr><td>Pipes</td><td>3.1.0</td><td><a
href="https://github.com/apache/sling-org-apache-sling-pipes";>GitHub</a>
- </td><td><a
href="[preferred]sling/org.apache.sling.pipes-3.1.0.jar">Bundle</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-3.1.0.jar.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-3.1.0.jar.sha1";>sha1</a>)
- </td><td><a
href="[preferred]sling/org.apache.sling.pipes-3.1.0-source-release.zip">Source
ZIP</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-3.1.0-source-release.zip.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-3.1.0-source-release.zip.sha1";>sha1</a>)
+
</td></tr><tr><td>Pipes</td><td>4.0.0</td><td><a
href="https://github.com/apache/sling-org-apache-sling-pipes";>GitHub</a>
+ </td><td><a
href="[preferred]sling/org.apache.sling.pipes-4.0.0.jar">Bundle</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-4.0.0.jar.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-4.0.0.jar.sha1";>sha1</a>)
+ </td><td><a
href="[preferred]sling/org.apache.sling.pipes-4.0.0-source-release.zip">Source
ZIP</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-4.0.0-source-release.zip.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.pipes-4.0.0-source-release.zip.sha1";>sha1</a>)
</td></tr><tr><td>Provisioning Model</td><td>1.8.6</td><td><a
href="https://github.com/apache/sling-org-apache-sling-provisioning-model";>GitHub</a>
</td><td><a
href="[preferred]sling/org.apache.sling.provisioning.model-1.8.6.jar">Bundle</a>
(<a
href="https://downloads.apache.org/sling/org.apache.sling.provisioning.model-1.8.6.jar.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.provisioning.model-1.8.6.jar.sha1";>sha1</a>)
</td><td><a
href="[preferred]sling/org.apache.sling.provisioning.model-1.8.6-source-release.zip">Source
ZIP</a> (<a
href="https://downloads.apache.org/sling/org.apache.sling.provisioning.model-1.8.6-source-release.zip.asc";>asc</a>,
<a
href="https://downloads.apache.org/sling/org.apache.sling.provisioning.model-1.8.6-source-release.zip.sha1";>sha1</a>)
