[SLING-6023] Context-Aware Config: Add pluggable context paths strategies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Context-Aware Configuration SPI 1.0.0, Context-Aware Configuration Impl 1.0.0
• Component/s: Extensions
• Labels: contextaware-config
• Assignee: Stefan Seifert
• Reporter: Stefan Seifert
• Created: 01/Sep/16 11:08
• Updated: 18/Oct/16 07:58
• Resolved: 19/Sep/16 15:39

Description

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.

Issue Links

• links to: GitHub Pull Request #171