You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2015/12/16 09:38:46 UTC
[jira] [Resolved] (OAK-3775) Inconsistency between
Node.getPrimaryType and Node.isNodeType
[ https://issues.apache.org/jira/browse/OAK-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved OAK-3775.
-------------------------
Resolution: Fixed
Applied proposed patch at revision 1720300.
[~mduerig], feel free to reopen this issue.
> Inconsistency between Node.getPrimaryType and Node.isNodeType
> --------------------------------------------------------------
>
> Key: OAK-3775
> URL: https://issues.apache.org/jira/browse/OAK-3775
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Amrit Verma
> Assignee: angela
> Fix For: 1.3.13
>
> Attachments: OAK-3775.patch
>
>
> Steps:
> 1. Create a node structure say /node1/node2 (node2 should be nt:hierarchyNode type node)
> 2. Create a testuser and grant read permission on whole repository.
> 3. Grant permission jcr:read to testuser on node2.
> 3. On node2, deny jcr:read to testuser with rep:glob=/*
> Execute the following from testuser's session:
> * {{node.getPrimaryNodeType().isNodeType(JcrConstants.NT_HIERARCHYNODE)}}
> * {{node.isNodeType(JcrConstants.NT_HIERARCHYNODE)}}
> where node refers to node2 created above. The first expression returns true but the second returns false.
> Expected: both should return true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)