You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/12 15:12:20 UTC
[jira] [Commented] (SLING-6023) Context-Aware Config: Add pluggable
context paths strategies
[ https://issues.apache.org/jira/browse/SLING-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484382#comment-15484382 ]
ASF GitHub Bot commented on SLING-6023:
---------------------------------------
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/171
SLING-6023 Context-Aware Config: Add pluggable context paths strategies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling feature/SLING-6023-config-contextpath-strategy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/171.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #171
----
commit 67012717c2b2031a7fea5ba39ff6f61801c344c1
Author: sseifert <ss...@pro-vision.de>
Date: 2016-09-12T12:59:05Z
SLING-6023 context path strategy SPI and default impl
commit c7cfbbfd5da1b13182177cd10121580d260f82c6
Author: sseifert <ss...@pro-vision.de>
Date: 2016-09-12T13:51:18Z
SLING-6023 make use of resource builder features in unit tests
commit aea839470bc387ed47851abbf9896d7c624ec345
Author: sseifert <ss...@pro-vision.de>
Date: 2016-09-12T14:39:08Z
SLING-6023 context path strategy multiplexer
commit 78546c7d6684c784e783762870c3c1b359abe71c
Author: sseifert <ss...@pro-vision.de>
Date: 2016-09-12T14:55:17Z
SLING-6023 use context path strategy multiplexer
commit 5f9356e9cc55e1edf91a9bec5b7c3727f62ae12e
Author: sseifert <ss...@pro-vision.de>
Date: 2016-09-12T15:08:39Z
Merge branch 'trunk' into feature/SLING-6023-config-contextpath-strategy
----
> 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 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)