Author: buildbot
Date: Wed May 17 20:01:36 2017
New Revision: 1012407
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 17 20:01:36 2017
@@ -1 +1 @@
-1795431
+1795449
Modified:
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html
Wed May 17 20:01:36 2017
@@ -146,11 +146,13 @@ h2:hover > .headerlink, h3:hover > .head
<li><code>/apps/conf</code> - because it is configured as fallback path</li>
<li><code>/libs/conf</code> - because it is configured as fallback path</li>
</ol>
-<p>So the basic rules are:
-<em> Go up in the content resource tree until a resource with
<code>sling:configRef</code> is found. This is the 'inner-most' context. Check
if a configuration resource exists at the path the property points to.
-</em> Check for parent resources of the references configuration resource
(below <code>/conf</code>)
-<em> Go further up in the content resource tree for parent contexts, and check
their configuration resources as well (they may reference completely different
location below <code>/conf</code>)
-</em> Check the fallback paths</p>
+<p>So the basic rules are:</p>
+<ul>
+<li>Go up in the content resource tree until a resource with
<code>sling:configRef</code> is found. This is the 'inner-most' context. Check
if a configuration resource exists at the path the property points to.</li>
+<li>Check for parent resources of the references configuration resource (below
<code>/conf</code>)</li>
+<li>Go further up in the content resource tree for parent contexts, and check
their configuration resources as well (they may reference completely different
location below <code>/conf</code>)</li>
+<li>Check the fallback paths</li>
+</ul>
<h1 id="configuration-persistence">Configuration persistence<a
class="headerlink" href="#configuration-persistence" title="Permanent
link">¶</a></h1>
<p>Example for the resource structure for a configuration resource at
<code>/conf/mysite</code>:</p>
<div class="codehilite"><pre><span class="o">/</span><span
class="n">conf</span>
@@ -189,7 +191,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>By defining a property <code>sling:configPropertyInherit</code> on the
configuration resource, property merging is enabled between the current
configuration resource and the next resource with the same name (singleton or
resource collection item) in the configuration resource lookup order. That
means that all properties that are not defined on the current configuration
resource are inherited from the next resources and a merged value map is used
for the configuration mapping.</p>
<p>By setting the property <code>sling:configPropertyInherit</code> on
multiple configuration resources that are part of the lookup order it is
possible to form deeper inheritance chains following the same rules.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1770354 by sseifert on Fri, 18 Nov 2016 09:38:15 +0000
+ Rev. 1795449 by sseifert on Wed, 17 May 2017 20:01:18 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
