[
https://issues.apache.org/jira/browse/JCR-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750543#action_12750543
]
Jukka Zitting commented on JCR-1865:
------------------------------------
> To ensure the session is authorized. Otherwise how do you ensure only
> authorized users use the facility?
By controlling access to the proposed ManagedRepository interface. My point is
that management operations like garbage collection, shutdown, etc. should be
outside the scope of normal client connections. This way we don't need to
invent new access control privileges for such operations.
> > Do we really need the MarkEventListener mechanism
> Yes, we do, it's important.
Why? Could we achieve the same use case with a simpler API?
> The current implementation can add an observation listener, and this needs to
> be removed.
Could the listener rather be passed as an argument to mark()?
PS. My concerns are a -0, not a veto. I just want to ensure that we strike the
best balance between exposed functionality and implementation flexibility.
Anything we put in o.a.j.api is something that we most likely need to live with
for at least the next 3-5 years.
> 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.
