[
https://issues.apache.org/jira/browse/SLING-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643631#comment-15643631
]
Stefan Seifert commented on SLING-6244:
---------------------------------------
Completed: At revision: 1768465
i've slightly changed the SPI method signature (swap parameter order) to make
it consistent with ConfigurationResourceResolvingStrategy, and added @NotNull
annotations.
question: should we support multiple SPI implementations via multiplexer here
as well? then we have to allow null as return value, and support multiple
services. maybe there are different deciders for different bucket names.
> Provide an SPI for influencing the collection inheritance
> ---------------------------------------------------------
>
> Key: SLING-6244
> URL: https://issues.apache.org/jira/browse/SLING-6244
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Context-Aware Configuration SPI 1.0.2, Context-Aware
> Configuration Impl 1.0.2
>
>
> Currently there is no way to influence the inheritance for collections as for
> example being implemented in DefaultConfigurationResourceResolvingStrategy
> We should provide an SPI which can be used by all strategy implementations:
> interface CollectionInheritanceDecider {
> enum DECISION {
> INCLUDE,
> EXCLUDE,
> BLOCK
> }
> DECISION decide(String bucketName, Resource resource);
> }
> So for every item found in getResourceCollection this optional service
> is asked. If it returns INCLUDE the resource is included, if it returns
> EXCLUDE it is excluded, but a parent can provide this resource. If it
> returns BLOCK, it's excluded and no parent can provide this resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
