[ https://issues.apache.org/jira/browse/SLING-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387746#comment-16387746 ]
Timothee Maret commented on SLING-7468: --------------------------------------- [~mpetria] I understand the point regarding preventing from serving as a generic entry point for editing configurations. However, we could still do a restricted implementation, without the explicit mapping. See my comment in https://issues.apache.org/jira/browse/SLING-7468?focusedCommentId=16352160&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16352160 Essentially we don't need to treat each factory individually, the factory we support all share common characteristics that we should exploit. In Sling speak, we could have a filter mechanism that acts on super type. > Allow to configure the Distribution Resource Provider > ----------------------------------------------------- > > Key: SLING-7468 > URL: https://issues.apache.org/jira/browse/SLING-7468 > Project: Sling > Issue Type: Improvement > Components: Content Distribution > Reporter: Timothee Maret > Assignee: Timothee Maret > Priority: Major > Fix For: Content Distribution Core 0.3.0 > > > SCD maintain its own Resource Provider > https://github.com/apache/sling-org-apache-sling-distribution-core/tree/master/src/main/java/org/apache/sling/distribution/resources > The implementation maps OSGI configurations and services as sling resources. > The implementation is not flexible to allow plugging a custom agent in the > resource tree. > The mapping seems to be done currently in enums, for instance > https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/component/impl/DistributionComponentKind.java > This issue is about making the configuration flexible (OSGI properties) or > even configuration-less (figure out the mappings at runtime). As a side > effect, the implementation may be simplified. > [~teofili],[~simone.tripodi] FYI -- This message was sent by Atlassian JIRA (v7.6.3#76005)