Stefan Seifert updated SLING-6023:
    Fix Version/s:     (was: Context-Aware Configuration API 1.0.0)
                   Context-Aware Configuration Impl 1.0.0
                   Context-Aware Configuration SPI 1.0.0

> 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
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration SPI 1.0.0, Context-Aware 
> Configuration Impl 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

Reply via email to