Hi Marco
As far as I remember the access control content is not versioned along with the
parent node it is attached to in the default implementation. This is indeed due
to the OPV flag set to IGNORE with the corresponding node type definitions.
However that cannot be changed and it is somewhat
+1
On Tue, Oct 30, 2018 at 11:21 PM Francesco Mari
wrote:
> +1
>
> On Tue, 30 Oct 2018 at 14:03, Michael Dürig wrote:
>
> >
> >
> > Hi,
> >
> > I intend to backport https://issues.apache.org/jira/browse/OAK-7838.
> > This fixes an unclosed executor (by removing it). The fix only affects
> >
Sure,
I'll add a JIRA for it with the test case. One more question, if I want to
separate the versioning of the node from the permission policy on it, can I
set the OPV to ignore for the relative rep:policy node? Or that just
doesn't work?
Marco
On Wed, Oct 31, 2018 at 8:52 AM Angela Schreiber
Hi Marco
Upon checkin of a versionable node (and it's non-versionable subtree) becomes
read-only. I think the first behavior is a bug. Changing permissions of a
checked-in node should not be possible. The reason why you are seeing it in the
second case is due to the fact that a mixin is
