[
https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139968#comment-16139968
]
Timothee Maret commented on SLING-6423:
---------------------------------------
I look at this issue and if we generalize it, it is about supporting the
FileVault AccessControlHandling.
The AccessControlHandling does not only cover MERGE, it also has plenty of
other modes that will likely be required at some point (CLEAR, IGNORE,
MERGE_PRESERVE and OVERWRITE).
Ideally, we don't re-implement those behaviour in Sling repoinit, and instead
keep the same logic in one place, in FileVault.
This would imply that I. we add a new dependency to the vault bundles in the
{{org.apache.sling.jcr.repoinit}} bundle and II. that the FileVault code may
need to be adapted to allow merging either documents (the XML representation of
nodes AFAIU) or regular nodes.
[~tripod] I am not that familiar with the FileVault code, but would it already
be possible to apply the merge logic between regular JCR nodes ? If not, would
it make sense to you to try factoring out the code to allow that ?
> Allow for specifying ACL merge mode (ACHandling) in repoinit
> ------------------------------------------------------------
>
> Key: SLING-6423
> URL: https://issues.apache.org/jira/browse/SLING-6423
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Reporter: Nitin Nizhawan
> Assignee: Timothee Maret
> Fix For: Repoinit Parser 1.1.2
>
> Attachments: SLING-6423_parser_changes.patch,
> SLING-6423_testcases.patch, SLING_6423_testcasesV2.patch
>
>
> Repoinit by default just add new ACLs if they are not already present.
> By contract package manager provides various strategies for ACL merging
> Extend repoinit to allow specifying these strategies
> https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/io/AccessControlHandling.html#MERGE
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
