jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeter Piegaze" <peeter.pieg...@day.com>
Subject Re: A question about versioning when OnParentVersion=VERSION
Date Mon, 17 Sep 2007 15:08:05 GMT
Hi Alexander,

Yes, this is the intended behavior. A subnode with OPV=VERSION is
meant to be an independently versionable item, not closely bound to
the parent node. What you probably want to do is make your subnode
OPV=COPY. This means that the subnode will be copied as part of the
frozen state of the parent node, then when the parent node is restored
the subnode is restored with it.


On 9/17/07, Alexander Nesterov <alex.maddriver@gmail.com> wrote:
> Hi,
> I don't fully understand how versioning works for nodes that have
> OnParentVersion attributes set to "VERSION". I have a versionable
> parent node with a child node versioned by it's own. When a new
> version of parent node is created it has a subnode representing the
> child node. The problem is that the child node has only
> jcr:childVersionHistory property which is a reference to it's version
> history but not a references to any particular version. Why the
> reference to version history but not to the particular version of
> child node is created? Without information about particular version
> it's impossible to revert parent and child nodes in future to the
> exact current state. Maybe i don't understand the design of versioning
> in JCR?
> TIA,
> --
> Alexander Nesterov

Peeter Piegaze

Day Software
Suite 331
67 Mowat Avenue
Toronto Ontario M6K 3E3

office +1 416 987 5720
mobile +1 647 205 2403
fax +1 866 719 3988

View raw message