[
https://issues.apache.org/jira/browse/SLING-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351739#comment-17351739
]
Bertrand Delacretaz commented on SLING-10228:
---------------------------------------------
As usual my memory doesn't help much about this but I dug in the code history
and it looks like this "optional nodetypes clause" test was added for
SLING-8602 ? I think the two {{-parser}} patches attached there introduced
those tests.
If that doesn't correspond to any JCR functionality I agree to deprecate these
statements. Throwing {{UnsupportedOperationException}} can be a good idea if we
clearly document the deprecation.
> Unused property PROP_NODETYPES in AclLine
> -----------------------------------------
>
> Key: SLING-10228
> URL: https://issues.apache.org/jira/browse/SLING-10228
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Angela Schreiber
> Priority: Major
>
> while performing some initial investigations for SLING-10219, i noticed that
> {{AclLine}} comes with a property {{AclLine.PROP_NODETYPES}}.
> while i found the following example in _test-33.txt_ , i couldn't find any
> usage in _org.apache.sling.jcr.repoinit_ or a more detailed explanation:
> {code}
> # Optional nodetypes clause
> deny jcr:lockManagement on /apps, /content nodetypes sling:Folder,
> nt:unstructured
> # nodetypes clause with restriction clause
> deny jcr:modifyProperties on /apps, /content nodetypes sling:Folder,
> nt:unstructured restriction(rep:itemNames,prop1,prop2)
> {code}
>
> therefore, i am bit lost what the intention behind that optional 'nodetypes'
> property would be in the first place as there exists no 'nodetypes' property
> with any type of access control entry defined by either JCR or Jackrabbit API.
> i would therefore suggest to deprecate and ignore it upon parsing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
