[
https://issues.apache.org/jira/browse/SLING-9862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222701#comment-17222701
]
Eric Norman commented on SLING-9862:
------------------------------------
[~dklco] Ok. I only suggested "txt" as the extension for simplicity. I
suppose one could use "-repoinit.txt" or something more declarative as the
matched extension instead.
One other benefit of using a jcr.contentloader extension is that you would also
get (for free) the ability to import the same via the post servlet via
":operation=import" which could be useful?
> 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)
