You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Draier (JIRA)" <ji...@apache.org> on 2010/01/22 16:43:21 UTC

[jira] Updated: (JCR-2474) Removing shareable node from a workspace and merging to another one removes the nodestate even if it's still shared

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

Thomas Draier updated JCR-2474:
-------------------------------

    Status: Patch Available  (was: Open)

> Removing shareable node from a workspace and merging to another one removes the nodestate even if it's still shared
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-2474
>                 URL: https://issues.apache.org/jira/browse/JCR-2474
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>    Affects Versions: 2.0-beta6
>            Reporter: Thomas Draier
>
> Hi again,
> Following the previous problem, when trying to remove one share of node D under B into ws1 , then merging A to ws2 completely removed the NodeState, even if it is still used under C.
> After that, the system is an inconsistent state - as node C still have a D child, but the D node does have any NodeState anymore.
> The issue can be located in VersionManagerImplMerge line 178 : calling :
> state.getState().removeChildNodeEntry(entry.getId())
> instead of :
> state.removeNode(entry.getName(), entry.getIndex())
> Regards

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.