[
https://issues.apache.org/jira/browse/JCRVLT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004515#comment-15004515
]
Tobias Bocanegra commented on JCRVLT-61:
----------------------------------------
today we have basically 2 modes: _replace_ or _merge_. where merge just adds
the new ACEs to the existing ACL, but only on a principal level. so it is not
possible to just _add_ a new ACE to the existing set of ACEs of 1 principal,
nor is it possible to completely remove all ACEs of 1 principal.
> Allow AccessControllHandling be defined per filter root
> -------------------------------------------------------
>
> Key: JCRVLT-61
> URL: https://issues.apache.org/jira/browse/JCRVLT-61
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Tobias Bocanegra
>
> the current packaging only allows to specify the AccessControllHandling per
> package. if one requires different behaviors for different content trees, the
> only workaround today is to create sub-packages.
> it would be nice if the ac-control handling can be defined by workspace
> filter root, similar to the iImportMode - or even tie the
> AccessControllHandling to the ImportMode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
