jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Michele (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2257) Removal of a node with shared subnodes fails
Date Wed, 12 Aug 2009 00:10:14 GMT

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

Lars Michele updated JCR-2257:

    Attachment: SessionItemStateManager.java.patch

The first patch prevents, that an event is fired on the remove of a share, when the parent
node of the share is deleted.
The second patch allows the correct calculation of the depth of a transient node, even if
a parent node is removed and in the attic.

> Removal of a node with shared subnodes fails
> --------------------------------------------
>                 Key: JCR-2257
>                 URL: https://issues.apache.org/jira/browse/JCR-2257
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-alpha7
>            Reporter: Lars Michele
>         Attachments: EventStateCollection.java.patch, SessionItemStateManager.java.patch
> A simple testcase:
> Set up (first transaction):
> Node a1 = testRootNode.addNode("a1");
> Node a2 = testRootNode.addNode("a2");
> a2.addMixin("mix:shareable");
> session.save();
> // now we have a shareable node N with path a2
> Workspace workspace = session.getWorkspace();
> String path = a1.getPath() + "/b1";
> workspace.clone(workspace.getName(), a2.getPath(), path, false);
> session.save();
> // now we have another shareable node N' in the same shared set as N with path a1/b1
> Test(second transaction):
> testRootNode.remove("a1");
> session.save();
> At least in a transactional repository the node will not be removed, an error will be
thrown instead.

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

View raw message