You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Lars Janssen (JIRA)" <ji...@apache.org> on 2013/05/13 16:51:16 UTC

[jira] [Updated] (JCR-3593) Updating a node causes properties of its versionable child to also be updated

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

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

    Summary: Updating a node causes properties of its versionable child to also be updated  (was: Updating a node causes properties of versionable child to also be updated)
    
> 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 believe 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.

--
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