[
https://issues.apache.org/jira/browse/JCR-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750912#action_12750912
]
Thomas Mueller commented on JCR-1865:
-------------------------------------
I think for the caller it shouldn't matter from _where_ the method is called
(client or server side). The implementation itself may throw an exception if
not implemented however.
> the implementation still doesn't have any access controls
The current implementation in Jackrabbit doesn't check access rights, that's
true. Of course we could implement it. In any case, an access rights check can
be implemented in a subclass.
Thinking about 'shutdown', what if we instead use instead:
// subject to access rights restrictions and availability
JackrabbitSession.getManagedRepository()
interface ManagedRepository {
getDataStoreGarbageCollector();
shutdown();
}
> Add the Data Store to the Jackrabbit API
> ----------------------------------------
>
> Key: JCR-1865
> URL: https://issues.apache.org/jira/browse/JCR-1865
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Attachments: api.patch, api_2.patch, core.patch, core_2.patch
>
>
> Currently, the garbage collection is not part of the Jackrabbit API. However,
> the data store garbage collection must be used once in a while if the data
> store is enabled. I propose to add the required interfaces to the Jackrabbit
> API. This will also allow to call garbage collection using RMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
