[
https://issues.apache.org/jira/browse/SLING-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386079#comment-16386079
]
Marius Petria commented on SLING-7468:
--------------------------------------
[~marett] I haven't looked yet at your patch but I wanted to share something
from the initial design intent. From a security perspective there should be
very little flexibility on what configs should be exposed as resources. We
should hardcode the exact osgi factories that are available through the
provider to avoid random osgi config editing. As I said, I do not know if your
patch violates this principle, so if the comment is misplaced please ignore it.
> 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)
