You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by gi...@apache.org on 2021/05/19 09:39:45 UTC
[sling-site] branch asf-site updated: Automatic website deployment
from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/165/
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 66bd118 Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/165/
66bd118 is described below
commit 66bd118a0af8e309871bbb190519f18462a1f688
Author: jenkins <bu...@apache.org>
AuthorDate: Wed May 19 09:39:42 2021 +0000
Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/165/
---
documentation/bundles/osgi-installer.html | 8 ++++++--
.../the-sling-engine/mappings-for-resource-resolution.html | 9 +++++++--
documentation/the-sling-engine/sling-api-crud-support.html | 4 ++--
documentation/the-sling-engine/url-decomposition.html | 4 ++--
documentation/the-sling-engine/wrap-or-decorate-resources.html | 8 ++++++--
5 files changed, 23 insertions(+), 10 deletions(-)
diff --git a/documentation/bundles/osgi-installer.html b/documentation/bundles/osgi-installer.html
index 681d288..74b913d 100644
--- a/documentation/bundles/osgi-installer.html
+++ b/documentation/bundles/osgi-installer.html
@@ -169,7 +169,11 @@
</ul>
<h2><a href="#health-check" id="health-check">Health Check</a></h2>
<p>The OSGi installer provides a <a href="/documentation/bundles/sling-health-check-tool.html">Sling Health Check</a> which validates that the processed OSGi installer resources have the correct state (<a href="https://issues.apache.org/jira/browse/SLING-5888">SLING-5888</a>). By default it will only check resources with a URL prefix <code>jcrinstall:/apps/</code>, so only the resources being provided through the <a href="/documentation/bundles/jcr-installer-provider.html">JCR Installer [...]
-<p>The health check will fail in the following cases: * Bundles Installation Failure * Configuration Installation Failure</p>
+<p>The health check will fail in the following cases:</p>
+<ul>
+<li>Bundles Installation Failure</li>
+<li>Configuration Installation Failure</li>
+</ul>
<h3><a href="#bundles-installation-failure" id="bundles-installation-failure">Bundles Installation Failure</a></h3>
<p>The checked bundle was not installed because it has been installed in a newer version from some other location (might even be through some other provider). For further details please look at the OSGi Installer console at <code>/system/console/osgi-installer</code> and check for all bundles with the given symbolic name (=OSGi installer's resource id) and their according URLs.</p>
<h3><a href="#configuration-installation-failure" id="configuration-installation-failure">Configuration Installation Failure</a></h3>
@@ -184,7 +188,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Wim Symons</span> on <span class="comment">Fri May 15 10:56:40 2020 +0200</span>
+ Last modified by <span class="author">Aravindo Wingeier</span> on <span class="comment">Wed May 19 11:36: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>
diff --git a/documentation/the-sling-engine/mappings-for-resource-resolution.html b/documentation/the-sling-engine/mappings-for-resource-resolution.html
index c7f11e9..eabab42 100644
--- a/documentation/the-sling-engine/mappings-for-resource-resolution.html
+++ b/documentation/the-sling-engine/mappings-for-resource-resolution.html
@@ -304,7 +304,12 @@ for (String segment: segments) {
<p>In general, the number of aliases have a direct impact on the performance of the resource resolution - as basically all possible permutations of paths for a resource have to be tested against the incoming request path. By default a cache is used to speed up handling aliases during resolving resources. It is highly recommended to have this cache enabled to avoid slowing down request performance. However, the cache might have an impact on startup time and on the alias update time if the [...]
<p>The cache can be disabled by setting the property <code>resource.resolver.optimize.alias.resolution</code> of the OSGi configuration <code>org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl</code> to <code>false</code>.</p>
<h3><a href="#limitation-of-slingalias-for-principal-with-a-limited-access" id="limitation-of-slingalias-for-principal-with-a-limited-access">Limitation of <code>sling:alias</code> for Principal with a limited access</a></h3>
-<p>Assuming there is * An User named <code>testuser</code> * An ACE with deny <code>jcr:all</code> in <code>/</code> for <code>everyone</code> * An ACE with allow <code>jcr:read</code> in <code>/content</code> for <code>testuser</code></p>
+<p>Assuming there is</p>
+<ul>
+<li>An User named <code>testuser</code></li>
+<li>An ACE with deny <code>jcr:all</code> in <code>/</code> for <code>everyone</code></li>
+<li>An ACE with allow <code>jcr:read</code> in <code>/content</code> for <code>testuser</code></li>
+</ul>
<p>If the <code>sling:alias</code> property (e.g. <code>myalias</code>) is set directly in <code>/content</code>, the User <code>testuser</code> will not be able to address the resource <code>/content</code> in an URL as <code>/myalias</code>. Instead if the <code>sling:alias</code> property is set in any resource under <code>/content</code> (e.g. <code>/content/visitors</code>) the <code>sling:alias</code> feature will work as usual.</p>
<h2><a href="#vanity-path-configuration" id="vanity-path-configuration">Vanity Path Configuration</a></h2>
<p>While an alias can provide a variation for a resource name, a vanity path can provide an alternative path for a resource. The following properties can be set on a resource:</p>
@@ -369,7 +374,7 @@ for (String segment: segments) {
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Konrad Windszus</span> on <span class="comment">Wed Nov 11 19:55:39 2020 +0100</span>
+ Last modified by <span class="author">Aravindo Wingeier</span> on <span class="comment">Wed May 19 11:36: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>
diff --git a/documentation/the-sling-engine/sling-api-crud-support.html b/documentation/the-sling-engine/sling-api-crud-support.html
index a461455..e5ab8ec 100644
--- a/documentation/the-sling-engine/sling-api-crud-support.html
+++ b/documentation/the-sling-engine/sling-api-crud-support.html
@@ -130,7 +130,7 @@
</ul>
<p>Which provide the ability to create and delete resources as well as the addition of the ModifiableValueMap interface which is similar to the ValueMap interface, but allows for updating properties on a resource.</p>
<h2><a href="#comparing-sling-api-crud-to-sling-post-servlet" id="comparing-sling-api-crud-to-sling-post-servlet">Comparing Sling API CRUD to Sling Post Servlet</a></h2>
-<p>Here are some examples of common operations performed using the Sling Post Servlet and Sling API CRUD support. Note, the examples are derived from the <a href="http://dev.day.com/content/ddc/blog/2008/07/cheatsheet/_jcr_content/images/cheatsheet/back.png">SlingPostServlet Cheatsheet</a>.</p>
+<p>Here are some examples of common operations performed using the Sling Post Servlet and Sling API CRUD support. Note, the examples are derived from the cheat sheet in Adobe's AEM documentation at <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html">https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html</a>.</p>
<h3><a href="#updating-a-property" id="updating-a-property">Updating a Property</a></h3>
<p>Update /myresource, setting the title and body:</p>
<p><strong>Sling Post Servlet</strong></p>
@@ -255,7 +255,7 @@ resourceResolver.commit();
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Thomas Morf</span> on <span class="comment">Sat Oct 5 02:13:49 2019 +0200</span>
+ Last modified by <span class="author">Aravindo Wingeier</span> on <span class="comment">Wed May 19 11:36: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>
diff --git a/documentation/the-sling-engine/url-decomposition.html b/documentation/the-sling-engine/url-decomposition.html
index 49a7fdc..68a66bd 100644
--- a/documentation/the-sling-engine/url-decomposition.html
+++ b/documentation/the-sling-engine/url-decomposition.html
@@ -128,7 +128,7 @@
</ol>
<p>In addition since <a href="https://issues.apache.org/jira/browse/SLING-848">SLING-848</a> there may be one or multiple <strong>request path parameters</strong> passed in the form <code>;<key>=<value></code>. Those request path parameters are only supported directly after the <em>Resource Path</em> or after the <em>Extension</em>. The value needs to be enclosed in <code>'</code> if it contains a <code>.</code> and is not located after the extension. It is up to the <a href [...]
<p>The decomposed parts can be accessed through the <code>RequestPathInfo</code> object, which is retrieved via <a href="https://sling.apache.org/apidocs/sling7/org/apache/sling/api/SlingHttpServletRequest.html#getRequestPathInfo--">SlingHttpServletRequest.getPathInfo()</a>.</p>
-<p>There's a cheat sheet in Adobe's AEM documentation at <a href="https://docs.adobe.com/docs/en/aem/6-2/develop/platform/sling-cheatsheet.html">https://docs.adobe.com/docs/en/aem/6-2/develop/platform/sling-cheatsheet.html</a> available to get you familiar with the URL decomposition of Sling.</p>
+<p>There's a cheat sheet in Adobe's AEM documentation at <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html">https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html</a> available to get you familiar with the URL decomposition of Sling.</p>
<h1><a href="#examples" id="examples">Examples</a></h1>
<p>Assume there is a Resource at <code>/a/b</code>, which has no children.</p>
<table>
@@ -168,7 +168,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Konrad Windszus</span> on <span class="comment">Fri Aug 14 10:29:33 2020 +0200</span>
+ Last modified by <span class="author">Aravindo Wingeier</span> on <span class="comment">Wed May 19 11:36: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>
diff --git a/documentation/the-sling-engine/wrap-or-decorate-resources.html b/documentation/the-sling-engine/wrap-or-decorate-resources.html
index 1a031d4..fe3ac6c 100644
--- a/documentation/the-sling-engine/wrap-or-decorate-resources.html
+++ b/documentation/the-sling-engine/wrap-or-decorate-resources.html
@@ -113,7 +113,11 @@
</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><h2><a href="#introduction" id="introduction">Introduction</a></h2>
-<p>The Sling API provides an easy way to wrap or decorate a resource before returning. Use cases for this could for example be * overwrite resource type/resource super type (for example based on the resource path) * add metadata</p>
+<p>The Sling API provides an easy way to wrap or decorate a resource before returning. Use cases for this could for example be</p>
+<ul>
+<li>overwrite resource type/resource super type (for example based on the resource path)</li>
+<li>add metadata</li>
+</ul>
<h2><a href="#"></a></h2>
<p>To add a resource decorator just register one or more services which implement the interface <code>ResourceDecorator</code></p>
<pre><code><!-- TODO syntax marker (::java) disabled -->interface ResourceDecorator {
@@ -139,7 +143,7 @@
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Thomas Wolfart</span> on <span class="comment">Tue Jul 17 21:15:24 2018 +0200</span>
+ Last modified by <span class="author">Aravindo Wingeier</span> on <span class="comment">Wed May 19 11:36: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>