[
https://issues.apache.org/jira/browse/SLING-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386222#comment-16386222
]
Marius Petria commented on SLING-7468:
--------------------------------------
Still, it is a very powerful tool: a (configurable) gate to configAdmin :). I
will try to understand the extensibility need in order to see if we can solve
it in a more restricted way. I fear that others might use it for their own
scenarios to access random configurations.
> 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)
