Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of crankydillo@gmail.com
 designates 209.85.134.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=ujANRM3+4Hodwe7gwaPa9Vaq738TVDRScrFQySgFoMU24QbO5eQ2jO+97z/o6MGyTh
         RFgeBq9/xHieeZ/+2QFBk+O/obTjmFMToLhwJ8WFz6DXIaToNQcjckVHtR+480wqscE3
         IhKfdcyppJA4csFgmDiW/OmhWfX5T1IeKNdps=
Message-ID: <4999BE18.5090908@gmail.com>
Date: Mon, 16 Feb 2009 13:27:20 -0600
From: Samuel Cox <crankydillo@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: Jackrabbit <users@jackrabbit.apache.org>
Subject: Versioning nodes to accomplish snapshot behavior
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I'm trying to give my users the ability to snapshot a hierarchy of 
documents.

For example, Let's say I have the following hierarchy where Ns are nodes 
and Ps are properties.

N1
|---------|
N2        N3
|---|     |---|
P   P     P   N4
               |
               P


My users can change Ps or add Ns a bunch of times and we don't generally 
care about those changes.  However, at some point in time we want to 
take a snapshot so that the current state of the hierarchy can be 
retrieved after future edits.

What I've been doing is marking the nodes as versionable and the 
removing the previous versions using 
VersionHistory.removeVersion(versionName).

Of course this gets kind of tricky.  For example, if I change N4.P, then 
I need to remove the versions created for N1, N3, and N4.

Does this sound crazy???

-- 
Samuel Cox