[jira] [Commented] (JCRVLT-359) Provide separate option to control handling of rep:cugPolicy nodes.

["Alexei Krainiouk (Jira)" <ji...@apache.org>]

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

Alexei Krainiouk commented on JCRVLT-359:
-----------------------------------------

[~tripod] rep:cugPolicy nodes are serialized into a package just fine. This is not a problem.

The problem in de-serialization (installation), which is controlled by aclHandling which applies equally to all policy nodes.

For replication we need rep:cugPolicy nodes handled differently from other ACL nodes and this is why separate configuration (cugHandling) option is proposed. For backwards compatibility when cugHandling policy is set to null (the default) deserialization of all ACL nodes is controlled by aclHandling as before.

I have created a [pull request|https://github.com/apache/jackrabbit-filevault/pull/56] that implements this idea.

> Provide separate option to control handling of rep:cugPolicy nodes.
> -------------------------------------------------------------------
>
>                 Key: JCRVLT-359
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-359
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>    Affects Versions: 3.2.8
>            Reporter: Alexei Krainiouk
>            Priority: Major
>
> Currently handling of rep:cugPolicy nodes is controlled by aclHandling configuration option that equally affects ACLs and CUGs. We need to control them separately as for replication that is based on sling-distribution we need to ignore ACLs while overwriting CUGs



--
This message was sent by Atlassian Jira
(v8.3.2#803003)