Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of gazarenkov@gmail.com
 designates 64.233.162.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:from;
        b=dlje2E7+fD9MGlwDr85LI28yQlbNQuifQGqu0pI7XuUR77XT2YEokQ3MhUZJ7bwLcB/t4erWHGLD42vv8oCE0Lhl8h54pXaU4/RcyOH3M8gEnR6AbOWl8D58KWP6pTuKmM/HPEuP32TqzCWLCu0gy86OPWZSmVK6zcRTSBcDa1A=
Message-ID: <020501c56fed$f4781590$f273020a@Gennady>
To: <jackrabbit-dev@incubator.apache.org>,
	<tobias.strasser@day.com>
References: <42A9B4D4.1050806@anyware-tech.com>
 <eb7e21905061104482c6d0cb4@mail.gmail.com>
 <42AAFEC4.4080508@anyware-tech.com>
 <8be731880506121151400825fe@mail.gmail.com>
Subject: Re: Getting VersionHistory after removing of a Node
Date: Mon, 13 Jun 2005 10:59:59 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
From: Gennady Azarenkov <gazarenkov@gmail.com>

Hi Tobias,

> since the creation of a VersionHistory is triggered by the creation of
> a mix:versionable node, the removal should happen automatically, as
> soon as no references to that version histroy exist anymore. this is
> the case, when all mix:versionable nodes (in all workspaces) belonging
> to that VH are deleted, and all the versions in the VH are removed

IMHO it is good behaviour if there is only one versionable node belonging to 
that VH
but i am not sure if it is correct to remove all versionable nodes (in all 
workspaces)
belonging to that VH (especially if versionable nodes from different 
workspaces
have base versions belong to different branches)?
i think we can not to change version history until there are at least one 
node connected to it
and remove the version history along with the last versionable connected to 
it as you suggest.

make sense?

Regards,
Gennady Azarenkov
eXo platform

----- Original Message ----- 
From: "Tobias Strasser" <tobias.strasser@gmail.com>
To: <jackrabbit-dev@incubator.apache.org>
Sent: Sunday, June 12, 2005 9:51 PM
Subject: Re: Getting VersionHistory after removing of a Node


> He may want to purge intermediate work versions of documents between
> each release (VersionGistory.removeVersion() is perfect for that), but
> also delete a document *and all its past revisions*, due to some legal
> requirements. For this last point, it seems JCR lacks a few
> functionnalities, as you also point out.

hi cederic,
since the creation of a VersionHistory is triggered by the creation of
a mix:versionable node, the removal should happen automatically, as
soon as no references to that version histroy exist anymore. this is
the case, when all mix:versionable nodes (in all workspaces) belonging
to that VH are deleted, and all the versions in the VH are removed
i.e. only the jcr:rootVersion is left. IMO, it is then safe to delete
the version history aswell.

i created a jira issue for this [JCR-134].
cheers, tobi

-- 
------------------------------------------< tobias.strasser@day.com >---
Tobias Strasser, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---