Author: buildbot
Date: Thu Sep 22 12:05:02 2016
New Revision: 997991

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    
websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Sep 22 12:05:02 2016
@@ -1 +1 @@
-1761914
+1761917

Modified: 
websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html
==============================================================================
--- 
websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html
 (original)
+++ 
websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html
 Thu Sep 22 12:05:02 2016
@@ -116,19 +116,21 @@ h2:hover > .headerlink, h3:hover > .head
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }</style>
 <div class="toc">
 <ul>
+<li><a href="#overview">Overview</a></li>
 <li><a href="#examples">Examples</a></li>
 <li><a href="#automated-tests">Automated Tests</a></li>
 </ul>
 </div>
-<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>
+<h1 id="overview">Overview<a class="headerlink" href="#overview" 
title="Permanent link">&para;</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 retrieving the resource path is implemented at <a 
href="https://sling.apache.org/apidocs/sling7/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-";>ResourceResolver.resolve(HttpServletRequest,String</a>.
 <em>It is impossible to tell from just looking at the request URI where the 
resource path part ends. You have to know the underlying resource structure to 
know how a URL is decomposed</em>.</li>
-<li><strong>Selectors</strong> -  If the first character in the request URL 
after the resource path is a dot, 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. If the resource path spans the complete request URL no seletors 
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. </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>
+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 retrieving the resource path is implemented at <a 
href="https://sling.apache.org/apidocs/sling7/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-";>ResourceResolver.resolve(HttpServletRequest,String)</a>.
 <em>It is impossible to tell from just looking at the request URI where the 
resource path part ends. You have to know the underlying resource structure to 
know how a URL is decomposed</em>.</li>
+<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>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>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 id="examples">Examples<a class="headerlink" href="#examples" 
title="Permanent link">&para;</a></h1>
 <p>Assume there is a Resource at <code>/a/b</code>, which has no children.</p>
@@ -259,12 +261,14 @@ Otherwise (for a path not matching any e
 </tbody>
 </table>
 <h1 id="automated-tests">Automated Tests<a class="headerlink" 
href="#automated-tests" title="Permanent link">&para;</a></h1>
-<p>The tests at
-<em> <a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/resourceresolver/src/test/java/org/apache/sling/resourceresolver/impl/ResourceResolverImplTest.java";>ResourceResolverImplTest</a>
 for the split between resource path and the rest. Mostly in the method 
<code>testbasicAPIAssumptions</code>.
-</em> <a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java";>SlingRequestPathInfoTest</a>
 demonstrates the decomposition after the resource path part.</p>
+<p>The tests at</p>
+<ul>
+<li><a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/resourceresolver/src/test/java/org/apache/sling/resourceresolver/impl/ResourceResolverImplTest.java";>ResourceResolverImplTest</a>
 shows the split between resource path and the rest. Mostly in the method 
<code>testBasicAPIAssumptions</code>.</li>
+<li><a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java";>SlingRequestPathInfoTest</a>
 demonstrates the decomposition after the resource path part.</li>
+</ul>
 <p>Feel free to suggest additional tests that help clarify how this works!</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; 
text-align: right;">
-        Rev. 1761914 by kwin on Thu, 22 Sep 2016 11:59:23 +0000
+        Rev. 1761917 by kwin on Thu, 22 Sep 2016 12:04:53 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache 
Sling project


Reply via email to