Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 84444 invoked from network); 3 Sep 2009 08:05:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Sep 2009 08:05:57 -0000 Received: (qmail 97631 invoked by uid 500); 3 Sep 2009 08:05:57 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 97589 invoked by uid 500); 3 Sep 2009 08:05:56 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 97546 invoked by uid 99); 3 Sep 2009 08:05:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 08:05:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 08:05:53 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E085D234C1E9 for ; Thu, 3 Sep 2009 01:05:32 -0700 (PDT) Message-ID: <1975429094.1251965132918.JavaMail.jira@brutus> Date: Thu, 3 Sep 2009 01:05:32 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1865) Add the Data Store to the Jackrabbit API In-Reply-To: <289230505.1227092384220.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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.