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

Oliver Lietz commented on SLING-9862:
-------------------------------------

[~cziegeler], You have a very specific use case with _the code bundle_ in mind. 
Sorry, I didn't realize *code* before and wouldn't put repoinit statements into 
a code bundle neither.

We have around a dozen _features_ (eventing, discovery, scripting, ...) in 
Sling where we set some configurations incl. service users and ACLs via 
repoinit – sensitive defaults which is IMHO totally fine and it's very unlikely 
that someone using Sling (didn't compare with AEM, but out of my head the paths 
are all the same) will change them.

Both Starter and Karaf bake the repoinit statements into configs which requires 
a custom distribution to change the configs and repoinit statements.

Moving the repoinit statements out of configs (scripts) into *a* dedicated 
bundle which has to be installed separately and reference them instead would at 
least allow to change the repoinit statements. This approach works fine with 
Pax URL Classpath.

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

Reply via email to