jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tobias Bocanegra <tri...@day.com>
Subject Re: moving node and versioning
Date Mon, 26 Apr 2010 19:52:34 GMT
hi,
when moving a node (i.e. Workspace or session move) or when cloning a
node to another workspace, it's uuid stays the same, thus referencing
the same version history. only if you workspace.copy a node to another
workspace, it will get a new uuid and get a new version history.

this behavior is the same in JCR 1.0 and JCR 2.0

regards, toby

On Mon, Apr 26, 2010 at 6:46 PM, Radu Ana-Maria <radu.anna@gmail.com> wrote:
> 10x..
> but i forgot to mention that i use jsr170.. it is the same?
>
> 10x.
> ana
>
>
>
> On Mon, Apr 26, 2010 at 6:37 PM, Justin Edelson <justinedelson@gmail.com>wrote:
>
>> From the JCR 2.0 Spec:
>>
>> 15.1.3 Moving Versionable Nodes
>> When an existing versionable node is moved to a new location with
>> Workspace.move or Session.move, it maintains the same version history
>> and no changes are made to that history.
>>
>>
>> On 4/26/10 5:34 AM, Radu Ana-Maria wrote:
>> > hello,
>> >
>> > i have a short question : if i move a node form an workspace to an other,
>> it
>> > version how is reacting? the version moves too?or not?
>> > (if yes the reference from the version is changed, yes? - because the new
>> > node has a new uuid-)
>> >
>> > any suggestion is appreciated!!
>> > many 10x
>> > ana
>> >
>>
>>
>

Mime
View raw message