[
https://issues.apache.org/jira/browse/SLING-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456541#comment-15456541
]
Stefan Seifert commented on SLING-6029:
---------------------------------------
Completed: At revision: 1758853
changed default folder name to {{/conf}} and renamed property to
{{sling:config-ref}}
open issue: the defaulting strategy does not yet respect the nested context
paths, and more unit tests for the different defaulting/inheritance use cases
need to be added.
> Context-Aware Config: Adapt defaulting strategy
> -----------------------------------------------
>
> Key: SLING-6029
> URL: https://issues.apache.org/jira/browse/SLING-6029
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: contextaware-config
>
> as discusesd in mail thread
> http://apache-sling.73963.n3.nabble.com/contextaware-config-Default-configuration-and-naming-td4064399.html
> we should change:
> * default folder name to /conf
> * rename the {{sling:config}} property name to {{sling:config-ref}}
> * and change the way default configuration is detected by following the
> example below
> for a content structure like this
> {noformat}
> /content
> /tenant1 - context path /content/tenant1
> /region1 - context path /content/tenant1/region1
> /site1 - context path /content/tenant1/region1/site1
> /page1
> {noformat}
> the configuration is looked up at this paths (in this order)
> {noformat}
> /conf/tenant1/region1/site1
> /conf/tenant1/region1
> /conf/tenant1
> /conf/global
> /apps/conf
> /libs/conf
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
