You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alexandre COLLIGNON (JIRA)" <ji...@apache.org> on 2015/11/11 16:31:10 UTC
[jira] [Comment Edited] (JCRVLT-61) Allow AccessControllHandling be
defined per filter root
[ https://issues.apache.org/jira/browse/JCRVLT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000517#comment-15000517 ]
Alexandre COLLIGNON edited comment on JCRVLT-61 at 11/11/15 3:30 PM:
---------------------------------------------------------------------
Hi [~tripod],
We're currently evaluating the possibility to define AccessControl handling on a per entry level which will offer a more fine-grained definition. We're considering these three options:
- insert first
- replace
- append
Do you think it's worth implementing both or should we consider it as a good replacement of this issue?
was (Author: acollign):
Hi [~tripod],
We're currently evaluating the possibility to define AccessControl handling on a per entry level which will offer a more fine-grained definition.
Do you think it's worth implementing both or should we consider it as a good replacement of this issue?
> 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)