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 0727e5d Automatic website deployment
0727e5d is described below
commit 0727e5d9911a61a738fe0c79d8aad2962da71bae
Author: jenkins <[email protected]>
AuthorDate: Tue Jul 9 07:36:57 2019 +0000
Automatic website deployment
---
documentation/the-sling-engine/resources.html | 34 ++++++++++++++++++++++++++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/documentation/the-sling-engine/resources.html
b/documentation/the-sling-engine/resources.html
index 793e904..aeb7206 100644
--- a/documentation/the-sling-engine/resources.html
+++ b/documentation/the-sling-engine/resources.html
@@ -202,6 +202,38 @@
<p>When accessing a Resource with path <code>/some/path/resource</code> the
Resource provider <em>R2</em> is first asked. If that cannot provide the
resource, Resource provider <em>R1</em> is asked and finally the JCR Resource
provider is asked. The first Resource provider having a Resource with the
requested path will be used.</p>
<h3><a href="#jcr-based-resources" name="jcr-based-resources">JCR-based
Resources</a></h3>
<p>JCR-based Resources are provided with the default
<code>JcrResourceProvider</code>. This Resource provider is always available
and is always asked last. That is Resources provided by other Resource
providers may never be overruled by repository based Resources.</p>
+<p>These are the authenticationInfo keys (which can be used with <a
href="https://sling.apache.org/apidocs/sling11/org/apache/sling/api/resource/ResourceResolverFactory.html#getResourceResolver-java.util.Map-";><code>ResourceResolverFactory.getResourceResolver(java.util.Map
authenticationInfo)</code></a>) which are supported by the
<code>JcrResourceProvider</code>:</p>
+<table>
+ <thead>
+ <tr>
+ <th>AuthenticationInfo Key </th>
+ <th>Type </th>
+ <th>Description </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><code>user.jcr.session</code> </td>
+ <td><code>javax.jcr.Session</code> </td>
+ <td>The session which is used for the underlying repository access. When
calling <code>close()</code> on the returned <code>ResourceResolver</code> the
session will not(!) be closed. </td>
+ </tr>
+ <tr>
+ <td><code>user.jcr.credentials</code> </td>
+ <td><code>javax.jcr.Credentials</code> </td>
+ <td>The credentials object from which to create the new underlying JCR
session</td>
+ </tr>
+ <tr>
+ <td><code>user.name</code> </td>
+ <td>String </td>
+ <td>Optionally used with <code>user.password</code> to create simple
credentials from which the Session is being created.</td>
+ </tr>
+ <tr>
+ <td><code>user.impersonation</code> </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>
<h3><a href="#bundle-based-resources"
name="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>
@@ -234,7 +266,7 @@
<p>The Sling API provides an easy way to wrap or decorate a resource before
returning. Details see <a
href="/documentation/the-sling-engine/wrap-or-decorate-resources.html">Wrap or
Decorate Resources</a>.</p></section></div></div>
<footer class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Philip Mundt</span>
on <span class="comment">Fri Aug 24 16:27:50 2018 +0200</span>
+ Last modified by <span class="author">Konrad
Windszus</span> on <span class="comment">Tue Jul 9 09:10:59 2019 +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>
