You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2018/02/03 07:17:00 UTC

[jira] [Commented] (SLING-7468) Allow to configure the Distribution Resource Provider

    [ https://issues.apache.org/jira/browse/SLING-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351293#comment-16351293 ] 

Tommaso Teofili commented on SLING-7468:
----------------------------------------

big +1 on my side as well, and btw I would opt for configuration-less (figure out mappings at runtime).

> 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
>
> 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)