[
https://issues.apache.org/jira/browse/SLING-9862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223164#comment-17223164
]
Carsten Ziegeler commented on SLING-9862:
-----------------------------------------
[~olli] Mainly for the reasons mentioned - the bundle developer does not know
the application configuration. You might want to use a different service user
name, a different path, even - for whatever reasons - different ACLs. If that
is all part of the bundle it is hard to change/override.
There is also the ordering problem, you need to make sure that repoinit is
executed before the code starts - possible, but sometimes requires additional
thinking/configuration.
If you keep repoinit outside of the bundle, you are not loosing anything, but
have a more flexible way - which already works today
> Support installing repoinit files listed in bundle header
> ---------------------------------------------------------
>
> Key: SLING-9862
> URL: https://issues.apache.org/jira/browse/SLING-9862
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.26
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Minor
>
> Implement support for a {{Sling-RepoInit}} bundle header that consists of a
> comma separated list of relative paths pointing to resources within the
> bundle. For each bundle with a non-empty {{Sling-RepoInit}} header, a
> {{SlingRepositoryInitializer}} that applies all repoinit files referenced in
> the header, should be dynamically registered.
> Such a mechanism would allow bundles to install their own service-user and
> corresponding ACLs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
