Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <5859080.post@talk.nabble.com>
Date: Thu, 17 Aug 2006 13:34:11 -0700 (PDT)
From: JavaJ <ponfar99@yahoo.com>
To: users@jackrabbit.apache.org
Subject: Re: More questions about versioning
In-Reply-To: <8be731880608170020o3af22809ldb2234f5abb33a71@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <5839690.post@talk.nabble.com>
 <8be731880608170020o3af22809ldb2234f5abb33a71@mail.gmail.com>


Thanks!  I read through the spec some more and it takes more sense now...

One more question:

Let's say you had a versionable NodeA (v1.2) with a versionable child node
NodeB (v1.0), with attribute onParentVersion=COPY.  You checkout NodeB and
add a new non-versionable node NodeC (onParentVersion=COPY) to NodeB, then
checkin a new version of NodeB (v1.1).  Although the spec doesn't seem to
specify what happens (if anything) to NodeA, I would think that the state of
NodeA in the version storage of v1.2 would have to be updated to include
NodeC as a new child of NodeB.  OR NodeA would have to be automatically
versioned to a new version v1.3 that includes NodeC as a child of NodeB. 
Otherwise, NodeA would be in an inconsistent state, because it would have a
base version of v1.2 which points to a state of NodeA in version storage
that does not include NodeC as a child of NodeB.  Does that sound right?


-- 
View this message in context: http://www.nabble.com/More-questions-about-versioning-tf2117527.html#a5859080
Sent from the Jackrabbit - Users forum at Nabble.com.