[OAK-928] Read access is enforced on NEW items

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13
• Component/s: core
• Assignee: Jukka Zitting
• Reporter: Angela Schreiber
• Created: 23/Jul/13 13:12
• Updated: 13/Dec/13 09:01
• Resolved: 02/Dec/13 13:14

Description

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:

              
    - return nodeBuilder.exists();
    + return nodeBuilder.isNew() || nodeBuilder.exists();
    

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

Issue Links

• blocks: OAK-869 Runtime exception while adding node
• relates to: OAK-923 Runtime exception while creating a group