jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1865) Add the Data Store to the Jackrabbit API
Date Thu, 03 Sep 2009 08:05:32 GMT

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

Jukka Zitting commented on JCR-1865:

My point here is that operations like garbage collection are IMHO not something that a JCR
client should be doing, especially when the implementation still doesn't have any access controls
and it relies on the client doing the right thing in the multi-repository case.

Nothing that we expose through a client-visible API should be able to break the internal consistency
of the repository.

Note that the garbage collection operation is in principle a "safe" operation so I'm not totally
opposed to putting it in a client-visible API, but until we either declare the multi-repository
data store configuration as unsupported or solve the obvious safety issue with this API I'm
quite reluctant to expose such functionality to all clients.

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

View raw message