[JCR-3885] Extend set of Actions in JackrabbitSession to reflect other operations than regular read/write

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.11.0
• Component/s: jackrabbit-api
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 05/Jun/15 12:00
• Updated: 17/Aug/15 07:57
• Resolved: 29/Jul/15 10:22

Description

Current the set of actions that can officially be passed to Session.hasPermission is limited to

Session.ACTION_ADD_NODE
Session.ACTION_SET_PROPERTY
Session.ACTION_REMOVE
Session.ACTION_READ

Consequently it is not possible to test if non-regular read/write operations can be execute permission wise.

As of Oak 1.0 this has been mitigated as the Session implementation present in oak-jcr also allows to pass the string representation of the built-in OAK Permissions. However, those constants are defined in the SPI part of oak-core and thus would require consumers to add a dependency to oak-core (which due to non-existing modularization includes tons of additional stuff include NodeStore), which feels totally wrong to me.

I would therefore like to propose to extend the set of action constants in JackrabbitSession such that API consumers can do everything with just using JCR and Jackrabbit API.

cc [e-mail], who asked about the best way to test a given permission setup and thus made me think about this.

Patch for API and oak will follow asap.

Issue Links

• is depended upon by: OAK-3160 Implement Session.hasPermission(String, String...) and support for additional actions