[ 
https://issues.apache.org/jira/browse/JCR-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379733#comment-14379733
 ] 

Alfusainey Jallow commented on JCR-3853:
----------------------------------------

[~anchela] yes, the build passes on my side! just one thing: do you want to 
place the `accessControlProvider.properties` file to the jcr2dav main/resources 
folder? that way, the standalone jar(when started) is able to load it as a 
resource(when a call to Session.getAccessControlManager() is made).

the reason is that we currently do not have a way to populate the 
`RepositoryConfig` in a non-test environment and a call to 
Session.getAccessControlManager(), from within a normal java program, will 
throw an `UnsupportedRepositoryOperationException`.

> JCR2SPI: Load ac provider resource
> ----------------------------------
>
>                 Key: JCR-3853
>                 URL: https://issues.apache.org/jira/browse/JCR-3853
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 2.9.1
>            Reporter: Alfusainey Jallow
>            Assignee: angela
>         Attachments: JCR-3853_1.patch, acprovider.patch
>
>
> Load the access control provider properties file as a resource. This fix uses 
> the class loader of the AccessControlProviderStub to load the resource



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

Reply via email to