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

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

     [ https://issues.apache.org/jira/browse/JCR-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella closed JCR-3885.
---------------------------------

Bulk close for 2.11.0

> Extend set of Actions in JackrabbitSession to reflect other operations than regular read/write
> ----------------------------------------------------------------------------------------------
>
>                 Key: JCR-3885
>                 URL: https://issues.apache.org/jira/browse/JCR-3885
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-api
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.11.0
>
>         Attachments: JCR-3885.patch
>
>
> Current the set of actions that can officially be passed to {{Session.hasPermission}} is limited to 
> {code}
> Session.ACTION_ADD_NODE
> Session.ACTION_SET_PROPERTY
> Session.ACTION_REMOVE
> Session.ACTION_READ
> {code}
> 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 [~pfaffm@adobe.com], 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)