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 481132a Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/132/
481132a is described below
commit 481132adcbc6083a068e9fe7f6e2a5f93026e87c
Author: jenkins <[email protected]>
AuthorDate: Thu Apr 1 10:22:55 2021 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/132/
---
documentation/bundles/scripting/scripting-htl.html | 135 ++++++++++-----------
1 file changed, 67 insertions(+), 68 deletions(-)
diff --git a/documentation/bundles/scripting/scripting-htl.html
b/documentation/bundles/scripting/scripting-htl.html
index 01adb11..c53630e 100644
--- a/documentation/bundles/scripting/scripting-htl.html
+++ b/documentation/bundles/scripting/scripting-htl.html
@@ -468,73 +468,72 @@ use // the use function
<h3><a href="#picking-the-best-use-provider-for-a-project"
id="picking-the-best-use-provider-for-a-project">Picking the best Use Provider
for a project</a></h3>
<p>The following table summarises the pros and cons for each Use Provider,
with the obvious exception of the Render Unit Use Provider.</p>
<table>
- <tr>
- <th>Use Provider</th>
- <th>Advantages</th>
- <th>Disadvantages</th>
- </tr>
- <tr>
- <td>Sling Models Use Provider</td>
- <td><ul><li>convenient injection annotations for data
retrieval</li><li>easy to extend from other Sling Models</li><li>simple setup
for unit testing</li></ul></td>
- <td><ul><li>lacks flexibility in terms of component overlaying,
relying on <code>service.ranking</code> configurations; this was solved for
Sling Models 1.3.0 by <a
href="https://issues.apache.org/jira/browse/SLING-5992";>SLING-5992</a></li></ul></td>
- </tr>
- <tr>
- <td>Java Use Provider</td>
- <td>
- <p>Use-objects provided through bundles:</p>
- <ul>
- <li>faster to initialise and execute than Sling Models for
similar code</li>
- <li>easy to extend from other similar Use-objects</li>
- <li>simple setup for unit testing</li>
- </ul>
- <p>Use-objects backed by <code>Resources</code>:</p>
- <ul>
- <li>faster to initialise and execute than Sling Models for
similar code</li>
- <li>easy to override from inheriting components through search
path overlay or by using the <code>sling:resourceSuperType</code> property,
allowing for greater flexibility</li>
- <li>business logic for components sits next to the HTL scripts
where the objects are used</li>
- </ul>
- </td>
- <td>
- <p>Use-objects provided through bundles:</p>
- <ul>
- <li>lacks flexibility in terms of component overlaying</li>
- </ul>
-<pre><code> <p>Use-objects backed by
<code>Resources</code>:</p>
- <ul>
- <li>cannot extend other Java objects</li>
- <li>the Java project might need a different setup to allow
running unit tests, since the objects will be deployed like content</li>
- </ul>
- </td>
-</tr>
-<tr>
- <td>JavaScript Use Provider</td>
- <td>
- <ul>
- <li>allows JavaScript developers to develop component
logic</li>
- <li>can be reused through the dependency mechanism provided
by the <code>use</code> function</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>harder to test and debug, relying mostly on end-to-end
testing and console logging</li>
- <li>slower to execute than both Sling Models and Java
Use-API objects</li>
- </ul>
- </td>
-</tr>
-<tr>
- <td>Script Use Provider</td>
- <td>
- <ul>
- <li>allows the usage of Use objects evaluated by other
Script Engines available in the platform</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>like in the case of the JavaScript Use Provider, the
performance is influenced by the Script Engine's implementation</li>
- </ul>
- </td>
-</tr>
-</code></pre>
+ <tr>
+ <th>Use Provider</th>
+ <th>Advantages</th>
+ <th>Disadvantages</th>
+ </tr>
+ <tr>
+ <td>Sling Models Use Provider</td>
+ <td><ul><li>convenient injection annotations for data
retrieval</li><li>easy to extend from other Sling Models</li><li>simple setup
for unit testing</li></ul></td>
+ <td><ul><li>lacks flexibility in terms of component overlaying, relying on
<code>service.ranking</code> configurations; this was solved for Sling Models
1.3.0 by <a
href="https://issues.apache.org/jira/browse/SLING-5992";>SLING-5992</a></li></ul></td>
+ </tr>
+ <tr>
+ <td>Java Use Provider</td>
+ <td>
+ <p>Use-objects provided through bundles:</p>
+ <ul>
+ <li>faster to initialise and execute than Sling Models for similar
code</li>
+ <li>easy to extend from other similar Use-objects</li>
+ <li>simple setup for unit testing</li>
+ </ul>
+ <p>Use-objects backed by <code>Resources</code>:</p>
+ <ul>
+ <li>faster to initialise and execute than Sling Models for similar
code</li>
+ <li>easy to override from inheriting components through search path
overlay or by using the <code>sling:resourceSuperType</code> property, allowing
for greater flexibility</li>
+ <li>business logic for components sits next to the HTL scripts where
the objects are used</li>
+ </ul>
+ </td>
+ <td>
+ <p>Use-objects provided through bundles:</p>
+ <ul>
+ <li>lacks flexibility in terms of component overlaying</li>
+ </ul>
+ <p>Use-objects backed by <code>Resources</code>:</p>
+ <ul>
+ <li>cannot extend other Java objects</li>
+ <li>the Java project might need a different setup to allow running
unit tests, since the objects will be deployed like content</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>JavaScript Use Provider</td>
+ <td>
+ <ul>
+ <li>allows JavaScript developers to develop component logic</li>
+ <li>can be reused through the dependency mechanism provided by the
<code>use</code> function</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>harder to test and debug, relying mostly on end-to-end testing and
console logging</li>
+ <li>slower to execute than both Sling Models and Java Use-API
objects</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td>Script Use Provider</td>
+ <td>
+ <ul>
+ <li>allows the usage of Use objects evaluated by other Script Engines
available in the platform</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>like in the case of the JavaScript Use Provider, the performance
is influenced by the Script Engine's implementation</li>
+ </ul>
+ </td>
+ </tr>
</table>
</section></div></div>
</div>
@@ -543,7 +542,7 @@ use // the use function
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">JE Bailey</span>
on <span class="comment">Fri Jul 13 09:06:26 2018 -0400</span>
+ Last modified by <span class="author">Radu
Cotescu</span> on <span class="comment">Thu Apr 1 12:19:29 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>
