[
https://issues.apache.org/jira/browse/JCRVLT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003749#comment-15003749
]
angela commented on JCRVLT-61:
------------------------------
[~tripod], yes, that looks promising. however, i have to admit that i keep
struggling with {{AccessControllHandling}} and the mapping of the individual
flags with the final outcome :-)
so, before making things more complicated with additional fine-grained ways to
define the intended setup, i would love to understand how it works nowadays,
what the exact limitations are and how something new would ultimately interact
with the existing package-level {{AccessControllHandling}}.
i haven't checked the documentation and neither looked at the existing
test-suite but i am happy to help you with a comprehensive coverage in case
this was missing... also to help me better understand the current behavior ;-)
> 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)
