Author: buildbot
Date: Thu Oct 13 21:23:55 2016
New Revision: 999387
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.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 13 21:23:55 2016
@@ -1 +1 @@
-1764784
+1764795
Modified:
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.html
Thu Oct 13 21:23:55 2016
@@ -192,10 +192,10 @@ Alternatively you can directly adapt you
<p>The ConfigurationBuilder also supports getting the configurations as
ValueMap or by adapting the configuration resources e.g. to a Sling Model. In
this case you have to specify a configuration name which is otherwise derived
automatically from the annotation class.</p>
<p>Internally the ConfigurationResolver used the ConfigurationResourceResolver
to get the configuration resources. It uses always the bucket name
<code>sling:configs</code>.</p>
<h1 id="contexts-and-configuration-references">Contexts and configuration
references<a class="headerlink" href="#contexts-and-configuration-references"
title="Permanent link">¶</a></h1>
-<p>When you use the <a href="">Default Implementation</a> contexts in the
content resource hierarchy is defined by setting <code>sling:config-ref</code>
properties. Each resource that has a <code>sling:config-ref</code> property set
defines the root resource of a context, the whole subtree is the context.
Within the subtree further nested contexts can be defined. The property
contains a resource path pointing to a resource below <code>/conf</code>. This
is the configuration reference.</p>
+<p>When you use the <a
href="http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html";>Default
Implementation</a> contexts in the content resource hierarchy is defined by
setting <code>sling:config-ref</code> properties. Each resource that has a
<code>sling:config-ref</code> property set defines the root resource of a
context, the whole subtree is the context. Within the subtree further nested
contexts can be defined. The property contains a resource path pointing to a
resource below <code>/conf</code>. This is the configuration reference.</p>
<p>Example:</p>
<p><img alt="Context and config reference"
src="context-and-config-reference.png" /></p>
-<p>If you define nested contexts or use a deeper hierarchy of resourced in
<code>/conf</code> the inheritance rules are applied. Additionally it is
possible to define default values as fallback if no configuration resource
exists yet in <code>/conf</code>. See <a href="">Default Implementation</a> for
details.</p>
+<p>If you define nested contexts or use a deeper hierarchy of resourced in
<code>/conf</code> the inheritance rules are applied. Additionally it is
possible to define default values as fallback if no configuration resource
exists yet in <code>/conf</code>. See <a
href="http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html";>Default
Implementation</a> for details.</p>
<h1 id="describe-configurations-via-annotation-classes">Describe
configurations via annotation classes<a class="headerlink"
href="#describe-configurations-via-annotation-classes" title="Permanent
link">¶</a></h1>
<p>You need an annotation class for each configuration you want to read via
the ConfigurationBuilder. The annotation classes may be provided by
the applications/libraries you use, or you can define your own annotation
classes for your application.</p>
@@ -280,15 +280,15 @@ the applications/libraries you use, or y
<h1 id="customizing-the-configuration-lookup">Customizing the configuration
lookup<a class="headerlink" href="#customizing-the-configuration-lookup"
title="Permanent link">¶</a></h1>
<p>The Context-Aware Configuration implementation provides a set of Service
Provider Interfaces (SPI) that allows you to overlay, enhance or replace the
default implementation and adapt it to your needs.</p>
-<p>See <a href="">SPI</a> for details.</p>
+<p>See <a
href="http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.html";>SPI</a>
for details.</p>
<h1 id="references">References<a class="headerlink" href="#references"
title="Permanent link">¶</a></h1>
<ul>
-<li><a href="">Context-Aware Configuration - Default Implementation</a></li>
-<li><a href="">Context-Aware Configuration - SPI</a></li>
+<li><a
href="http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.html";>Context-Aware
Configuration - Default Implementation</a></li>
+<li><a
href="http://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration-spi.html";>Context-Aware
Configuration - SPI</a></li>
<li><a
href="https://adapt.to/2016/en/schedule/sling-context-aware-configuration.html";>Sling
Context-Aware Configuration - Talk from adaptTo() 2016</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1764680 by sseifert on Thu, 13 Oct 2016 13:56:47 +0000
+ Rev. 1764795 by sseifert on Thu, 13 Oct 2016 21:23:47 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
