Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Mon, 13 May 2013 14:55:15 +0000 (UTC)
From: "Lars Janssen (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12647312.1368456457959.309716.1368456915909@arcas>
In-Reply-To: <JIRA.12647312.1368456457959@arcas>
References: <JIRA.12647312.1368456457959@arcas>
Subject: [jira] [Updated] (JCR-3593) Updating a node causes properties of
 its versionable child to also be updated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Janssen updated JCR-3593:
------------------------------

    Description: 
Given a workspace "preview" with node "/fooBar", and a child node "/fooBar/fooBarChild" (with mix:versionable), I am attempting the following:

1. Clone /fooBar to a second workspace, "published"
2. In the original "preview" workspace, change a property of fooBar, change a property of fooBarChild
3. Update node "/fooBar" in the "published" workspace from the "preview" workspace

Expected behaviour:

After steps 1 and 2, both workspaces contain identical nodes and properties.
After step 3, in the "published" workspace the "fooBar" node has an updated property, but "fooBarChild" is the same as after step 2. This is because the child is versionable, and I understand versionable nodes will be skipped.

Actual behaviour: 

After steps 1 and 2, both workspaces and nodes are as expected.
After step 3, in the "published" workspace the "fooBar" node is updated as expected; the child node "fooBarChild" is also updated, and this was not expected.

The following Gist contains a demonstration: https://gist.github.com/fazy/5568416

There was also discussion of this on the Jackrabbit mailing list: http://www.mail-archive.com/users@jackrabbit.apache.org/msg19362.html

Of course, it's possible I'm wrong about the expected behaviour, so I would appreciate any feedback on that.

  was:
Given a workspace "preview" with node "/fooBar", and a child node "/fooBar/fooBarChild" (with mix:versionable), I am attempting the following:

1. Clone /fooBar to a second workspace, "published"
2. In the original "preview" workspace, change a property of fooBar, change a property of fooBarChild
3. Update node "/fooBar" in the "published" workspace from the "preview" workspace

Expected behaviour:

After steps 1 and 2, both workspaces contain identical nodes and properties.
After step 3, in the "published" workspace the "fooBar" node has an updated property, but "fooBarChild" is the same as after step 2. This is because the child is versionable, and I understand versionable nodes will be skipped.

Actual behaviour: 

After steps 1 and 2, both workspaces and nodes are as expected.
After step 3, in the "published" workspace the "fooBar" node is updated as expected; the "fooBarChild" is also updated, and this was not expected.

The following Gist contains a demonstration: https://gist.github.com/fazy/5568416

There was also discussion of this on the Jackrabbit mailing list: http://www.mail-archive.com/users@jackrabbit.apache.org/msg19362.html

Of course, it's possible I'm wrong about the expected behaviour, so I would appreciate any feedback on that.

    
> Updating a node causes properties of its versionable child to also be updated
> -----------------------------------------------------------------------------
>
>                 Key: JCR-3593
>                 URL: https://issues.apache.org/jira/browse/JCR-3593
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6
>         Environment: Running on Debian Wheezy 64-bit, java -version gives:
>     Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
>     Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
>            Reporter: Lars Janssen
>
> Given a workspace "preview" with node "/fooBar", and a child node "/fooBar/fooBarChild" (with mix:versionable), I am attempting the following:
> 1. Clone /fooBar to a second workspace, "published"
> 2. In the original "preview" workspace, change a property of fooBar, change a property of fooBarChild
> 3. Update node "/fooBar" in the "published" workspace from the "preview" workspace
> Expected behaviour:
> After steps 1 and 2, both workspaces contain identical nodes and properties.
> After step 3, in the "published" workspace the "fooBar" node has an updated property, but "fooBarChild" is the same as after step 2. This is because the child is versionable, and I understand versionable nodes will be skipped.
> Actual behaviour: 
> After steps 1 and 2, both workspaces and nodes are as expected.
> After step 3, in the "published" workspace the "fooBar" node is updated as expected; the child node "fooBarChild" is also updated, and this was not expected.
> The following Gist contains a demonstration: https://gist.github.com/fazy/5568416
> There was also discussion of this on the Jackrabbit mailing list: http://www.mail-archive.com/users@jackrabbit.apache.org/msg19362.html
> Of course, it's possible I'm wrong about the expected behaviour, so I would appreciate any feedback on that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira