[
https://issues.apache.org/jira/browse/OAK-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637986#comment-13637986
]
Jukka Zitting commented on OAK-787:
-----------------------------------
Looks OK to me, though I'd like it a bit better if these cases only applied to
children of /jcr:system instead of anywhere in the content tree. For example,
if I (for whatever reason) made a copy of the jcr:nodeTypes registry under some
other path, then that copy should fall under normal access control rules.
> Accessibility of NodeTypes, Namespaces and Privileges
> -----------------------------------------------------
>
> Key: OAK-787
> URL: https://issues.apache.org/jira/browse/OAK-787
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: angela
> Assignee: angela
> Attachments: OAK-787.patch
>
>
> in jackrabbit-core node types, namespaces and privileges were stored
> separated from the repository content in the file system. accessibility
> of that part of the repository was therefore never managed by the
> regular item access in jackrabbit.
> now, as of oak all of them are stored and accessed in the repository
> and are consequently affected by regular item read access which
> basically breaks backwards compatibility.
> we should define means of asserting backwards compatible behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
