Author: sseifert
Date: Thu Oct 13 13:36:35 2016
New Revision: 1764672
URL: http://svn.apache.org/viewvc?rev=1764672&view=rev
Log:
Context-Aware Configuration docs
Added:
sling/site/trunk/content/documentation/bundles/context-aware-configuration.mdtext
- copied, changed from r1764671,
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
Removed:
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
Copied:
sling/site/trunk/content/documentation/bundles/context-aware-configuration.mdtext
(from r1764671,
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext)
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/context-aware-configuration.mdtext?p2=sling/site/trunk/content/documentation/bundles/context-aware-configuration.mdtext&p1=sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext&r1=1764671&r2=1764672&rev=1764672&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration.mdtext
(original)
+++
sling/site/trunk/content/documentation/bundles/context-aware-configuration.mdtext
Thu Oct 13 13:36:35 2016
@@ -8,7 +8,7 @@ These bundles provide a service API that
Here is an example how your content structure may look like:
-
+
The application needs different configuration for different sites, regions and
tenants = different contexts. Some parameters may be shared, so inheritance for
nested contexts and from global fallback values is supported as well. You have
full control which content subtrees are the contexts in your application, the
structure above is only an example.
@@ -86,7 +86,7 @@ When you use the [Default Implementation
Example:
-
+
If you define nested contexts or use a deeper hierarchy of resourced in
`/conf` the inheritance rules are applied. Additionally it is possible to
define default values as fallback if no configuration resource exists yet in
`/conf`. See [Default Implementation]({{
ref.context-aware-config-default-implementation.path }}) for details.