diff --git a/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/aem/AcToolCqActions.java b/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/aem/AcToolCqActions.java index 42a93a95..31407f77 100644 --- a/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/aem/AcToolCqActions.java +++ b/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/aem/AcToolCqActions.java @@ -30,7 +30,16 @@ import biz.netcentric.cq.tools.actool.configmodel.AceBean; import biz.netcentric.cq.tools.actool.helper.AccessControlUtils; -/** Mimics the behaviour of the now deprecated CqActions class (behaviour should be in line with cq-security-5.6.2.) */ +/** Mimics the behaviour of the now deprecated CqActions class (behaviour should be in line with cq-security-5.6.2.) + * CqActions are an abstraction on top of JCR privileges to act on Page level (i.e. dedicated privileges for some node types). + * + * This requires handling ACEs on two logical levels (they are maintained in the same ACList, but one is having a {@code rep:glob} restriction): + *
    + *
  1. top level for the rights which apply to all nodes (sub pages as well as page content nodes)
  2. + *
  3. jcr:content level restrictions for the rights which apply only to nodes within the page content
  4. + *
+ * + */ public class AcToolCqActions { private static final Logger LOG = LoggerFactory.getLogger(AcToolCqActions.class);