[
https://issues.apache.org/jira/browse/JCR-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751071#action_12751071
]
Jukka Zitting commented on JCR-1865:
------------------------------------
I branched the general discussion about a management API to the dev@ list.
Let's focus on the specific garbage collection issue here.
I'm ready to accept the JackrabbitSession.createGarbageCollector() approach.
However, the following concerns still stand:
* How do we protect against the multi-repository sweep() issue? I would be fine
either with simply not supporting such deployments, or with enforcing
administrator-only access to the garbage collection feature.
* Does the MarkEventListener interface need to extend EventListener?
* Do we need separate before/after events?
* Do the event methods need a Node argument, or would a path (or identifier)
string be enough?
* Is the done() event needed or could the same information be inferred from the
mark() method returning?
> 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
> Fix For: 2.0.0
>
> 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.
