[
https://issues.apache.org/jira/browse/SLING-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643644#comment-15643644
]
Carsten Ziegeler commented on SLING-6244:
-----------------------------------------
[~sseif...@pro-vision.de] Yes, I think having multiple implementations makes
sense as there could be different implementations for different buckets.
So we would call the services in service ranking order (highest first), the
first one returning a non null value is used for the decision
> 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)
