You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/09/01 11:08:20 UTC
[jira] [Created] (SLING-6023) Context-Aware Config: Add pluggable
context paths strategies
Stefan Seifert created SLING-6023:
-------------------------------------
Summary: Context-Aware Config: Add pluggable context paths strategies
Key: SLING-6023
URL: https://issues.apache.org/jira/browse/SLING-6023
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Fix For: Context-Aware Configuration 1.0.0
by default the context paths for which configurations can be linked are defined by the existence of a {{sling:config}} property on that node.
we want to keep this as default behavior, but this is getting cumbersome if a "massive multi-tenant scenario" is used with hundreds of sites grouped by regions etc. that follow up a consistent repository scheme. in this case it would be easier to not to be forced to create a sling:config property on each site root and link it to the correct configuration (and move it when the site is moved), but to provide an own strategy implementation how these context paths are detected.
new strategies can be registered as OSGi services, service ranking controls which is asked first. via a service property it should be possible to register a special strategy only for a subpath e.g. /content/tenant1 it should apply to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)