[jira] [Created] (OAK-928) Read access is enforced on NEW items

["angela (JIRA)" <ji...@apache.org>]

angela created OAK-928:
--------------------------

             Summary: Read access is enforced on NEW items
                 Key: OAK-928
                 URL: https://issues.apache.org/jira/browse/OAK-928
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core
            Reporter: angela


as explained in OAK-923 we may currently run into the situation where a new Tree is being added because it does not exist but the resulting child does not exist due to restricted access. the same is true for new properties.

IMHO this breaks backwards compatibility with jackrabbit core.

i would therefore suggest to
- extend MutableTree#exists by checking for the tree being new
  line 390: 
  {noformat}            
  - return nodeBuilder.exists();
  + return nodeBuilder.isNew() || nodeBuilder.exists();
  {noformat}
- similar behavior for #hasProperty #getProperty, #getProperties and #getPropertyCount (no patch yet).

however, i would like to get a broader consensus on this kind of modifications as this
might have side effects in other places.



--
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