Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 69303 invoked from network); 5 May 2008 07:49:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 May 2008 07:49:58 -0000 Received: (qmail 95896 invoked by uid 500); 5 May 2008 07:49:59 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 95871 invoked by uid 500); 5 May 2008 07:49:58 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 95860 invoked by uid 99); 5 May 2008 07:49:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2008 00:49:58 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [81.19.98.213] (HELO eul0600252.eu.verio.net) (81.19.98.213) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2008 07:49:11 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by eul0600252.eu.verio.net (Postfix) with ESMTP id 921FA53C35 for ; Mon, 5 May 2008 09:48:25 +0200 (CEST) Received: from eul0600252.eu.verio.net ([127.0.0.1]) by localhost (eul0600252 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08743-05 for ; Mon, 5 May 2008 09:48:25 +0200 (CEST) Received: from [192.168.1.4] (200.106.219.87.dynamic.jazztel.es [87.219.106.200]) by eul0600252.eu.verio.net (Postfix) with ESMTP id 4EE6153C1D for ; Mon, 5 May 2008 09:48:25 +0200 (CEST) Subject: Re: undo deletion of a node (re-post) From: Paco Avila To: users@jackrabbit.apache.org In-Reply-To: <91f3b2650805042334i1736c9f8w3faa308e61ccd13e@mail.gmail.com> References: <403316910805011236x7e8e6385m532a39c74dfeaa6@mail.gmail.com> <91f3b2650805042334i1736c9f8w3faa308e61ccd13e@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Organization: GIT Consultors Date: Mon, 05 May 2008 09:49:21 +0200 Message-Id: <1209973761.6312.1.camel@monkiki.git.es> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at git.es X-Virus-Checked: Checked by ClamAV on apache.org You can simulate the deletion moving the node to another "trash" folder node where you put all "deleted" nodes before a purge (the true delete action :) El lun, 05-05-2008 a las 08:34 +0200, Thomas Müller escribió: > Hi, > > I don't think it is possible except for the workarounds you have described. > > Regards, > Thomas > > On Thu, May 1, 2008 at 9:36 PM, Rob Esposito wrote: > > Apologies for the re-post. I was afraid I wasn't getting responses because > > I may have been too verbose the first time around. > > > > I'm looking for a way to recreate a node which has been deleted with the > > same UUID without affecting the version history and without storing a copy > > of it in another branch of the repository. Is this possible? > > > > thanks, > > rob > > > > ---------- Forwarded message ---------- > > Date: Thu, Apr 10, 2008 at 5:59 PM > > Subject: undo delete node > > To: users@jackrabbit.apache.org > > > > > > Hi all, > > > > We are developing an application containing a GUI which allows users to > > manipulate nodes in a JCR repository. We're wondering if there is a > > recommended way of restoring a node that has been deleted or removed. For > > example, if a user wishes to undo the deletion of a node. We've come across > > two different approaches, but neither of them seem to be the solution we're > > looking for. > > > > The first approach was in a post ( > > http://www.nabble.com/restoring-removed-node-td8182449.html#a8203066) and it > > suggests using a 'Recycle Bin' type node to store the parent node > > path/uuid. The problem with this method is that you are left with the > > decision of when/how to clean up the nodes in the 'Recycle Bin'. > > > > The other approach we've been using is to store the state of the node just > > before deletion using Session.exportSystemView and to bring it back using > > Session.importXML. The problem with this method is that, after an > > importXML, the restored node is checked out with base version set to > > rootVersion. The expectation is that the user will have to check this node > > back in and the version history will branch each time this happens. > > > > So essentially, what we're looking for is a way to recreate a node with the > > same UUID without affecting the version history or storing a copy of it in > > another branch of the repository. Is this possible? > > -- Paco Avila GIT Consultors