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 c2b12c9 Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/131/
c2b12c9 is described below
commit c2b12c947780c11a1769b0fff5ceb37525d06f5d
Author: jenkins <[email protected]>
AuthorDate: Wed Mar 31 10:47:21 2021 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/131/
---
documentation/bundles/sling-pipes/bindings.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/bundles/sling-pipes/bindings.html
b/documentation/bundles/sling-pipes/bindings.html
index f3575cf..4f1578d 100644
--- a/documentation/bundles/sling-pipes/bindings.html
+++ b/documentation/bundles/sling-pipes/bindings.html
@@ -117,7 +117,7 @@
</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 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>
+<p>You can also set whatever scripting engine you want per pipe (including
nashorn, rhino, groovy, ...) by setting, at the root pipe level, the property
<code>engine</code> to the engine name (as it's registered) you wish.</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>
@@ -175,7 +175,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">Thu Jan 28 17:14:27 2021 +0100</span>
+ Last modified by <span class="author">Nicolas
Peltier</span> on <span class="comment">Wed Mar 31 12:42:27 2021 +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>
