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 da9ecd3 Automatic website deployment from
https://builds.apache.org/job/Sling/job/sling-site/job/master/418/
da9ecd3 is described below
commit da9ecd395293b754ea0170c9431e9fdd0afa29a8
Author: jenkins <[email protected]>
AuthorDate: Thu Aug 6 10:28:00 2020 +0000
Automatic website deployment from
https://builds.apache.org/job/Sling/job/sling-site/job/master/418/
---
documentation/the-sling-engine/resources.html | 11 ++++++++++-
documentation/the-sling-engine/url-decomposition.html | 7 ++++---
2 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/documentation/the-sling-engine/resources.html
b/documentation/the-sling-engine/resources.html
index 06da1a9..29cd6f8 100644
--- a/documentation/the-sling-engine/resources.html
+++ b/documentation/the-sling-engine/resources.html
@@ -225,6 +225,15 @@
<tr><td> <code>user.impersonation</code> </td><td> <a
href="https://sling.apache.org/apidocs/sling11/org/apache/sling/api/resource/ResourceResolverFactory.html#USER_IMPERSONATION";><code>ResourceResolverFcatory.USER_IMPERSONATION</code></a>
</td><td> String </td><td> User ID which should be used for impersonation via
<code>javax.jcr.Session.impersonate(...)</code>. Must be combined with one of
the other authentication info keys.</td></tr>
</tbody>
</table>
+<p>There is support for the following <a href="url-decomposition.html">path
parameters</a>:</p>
+<table>
+<thead>
+<tr><th>Path Parameter </th><th> Example Value </th><th> Description </th><th>
Since</th></tr>
+</thead>
+<tbody>
+<tr><td> <code>v</code> </td><td> <code>1.0</code> </td><td> Retrieves the
underlying JCR node from the <a
href="https://docs.adobe.com/docs/en/spec/jcr/2.0/15_Versioning.html";>version
history</a> leveraging the version label given in the value. </td><td> <a
href="https://issues.apache.org/jira/browse/SLING-848";>SLING-848</a></td></tr>
+</tbody>
+</table>
<h3><a href="#bundle-based-resources" id="bundle-based-resources">Bundle-based
Resources</a></h3>
<p>Resources may by provided by OSGi bundles. Providing bundles have a Bundle
manifest header <code>Sling-Bundle-Resources</code> containing a list of
absolute paths provided by the bundle. The path are separated by comma or
whitespace (SP, TAB, VTAB, CR, LF).</p>
<p>The <code>BundleResourceProvider</code> supporting bundle-based Resources
provides directories as Resources of type <code>nt:folder</code> and files as
Resources of type <code>nt:file</code>. This matches the default primary node
types intended to be used for directories and files in JCR repositories.</p>
@@ -262,7 +271,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">Thu Dec 5 16:01:11 2019 +0100</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Thu Aug 6 10:00:58 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/the-sling-engine/url-decomposition.html
b/documentation/the-sling-engine/url-decomposition.html
index f80ff16..61c7296 100644
--- a/documentation/the-sling-engine/url-decomposition.html
+++ b/documentation/the-sling-engine/url-decomposition.html
@@ -123,12 +123,13 @@
<h1><a href="#overview" id="overview">Overview</a></h1>
<p>During the <em>Resource Resolution</em> step, the client request URI (as
being returned by <a
href="http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI()">HttpServletRequest.getRequestURI()</a>)
is decomposed into the following parts (in exactly this order):</p>
<ol>
-<li><strong>Resource Path</strong> - For existing resources the resource path
is the longest match (also considering its <a
href="/documentation/the-sling-engine/mappings-for-resource-resolution.html">mappings</a>)
pointing to a resource where the next character is either a dot
(<code>.</code>) or it is the full request URI. Otherwise (for a path not
matching any existing resource) the resource path ends at the <em>first dot
(<code>.</code>)</em> in the request url. The exact logic for r [...]
+<li><strong>Resource Path</strong> - For existing resources the resource path
is the longest match (also considering its <a
href="/documentation/the-sling-engine/mappings-for-resource-resolution.html">mappings</a>)
pointing to a resource where the next character is either a dot
(<code>.</code>) or it is the full request URI. Otherwise (for a path not
matching any existing resource) the resource path ends at the <em>first dot
(<code>.</code>)</em> in the request url. The exact logic for r [...]
<li><strong>Selectors</strong> - If the first character in the request URL
after the resource path is a dot (<code>.</code>), the string after the dot up
to but not including the last dot before the next slash character or the end of
the request URL comprises the selectors. If the resource path spans the
complete request URL no selectors exist. If only one dot follows the resource
path before the end of the request URL or the next slash, also no selectors
exist.</li>
<li><strong>Extension</strong> - The string after the last dot after the
resource path in the request URL but before the end of the request URL or the
next slash after the resource path in the request URL is the extension.</li>
<li><strong>Suffix</strong> - If the request URL contains a slash character
after the resource path and optional selectors and extension, the path starting
with the slash up to the end of the request URL is the suffix path. Otherwise,
the suffix path is empty. Note, that after the resource path at least a dot
must be in the URL to let Sling detect the suffix.</li>
</ol>
-<p>Those 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>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 hr [...]
+<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>
<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>
@@ -167,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 Jul 13 11:08:10 2018 +0200</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Thu Aug 6 10:00:58 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>
