You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2010/07/21 13:25:52 UTC

[jira] Created: (JCR-2683) Provide rename method for nodes

Provide rename method for nodes
-------------------------------

                 Key: JCR-2683
                 URL: https://issues.apache.org/jira/browse/JCR-2683
             Project: Jackrabbit Content Repository
          Issue Type: New Feature
          Components: jackrabbit-api, jackrabbit-core
    Affects Versions: 2.2.0
            Reporter: Michael Dürig
            Priority: Minor


Currently renaming a node is a nuisance if the node's parent has orderable child nodes: The parents child nodes must be searched for the successor of the node to be moved, the node must be moved to its new name and then ordered before the successor. Furthermore the case where the to be moved node is the last node must be special cased. 

I thus propose to provide functionality for directly renaming nodes.  

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

[jira] Resolved: (JCR-2683) Provide rename method for nodes

Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.

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

Stefan Guggisberg resolved JCR-2683.
------------------------------------

    Fix Version/s: 2.2.0
       Resolution: Fixed

added 
    
    o.a.jackrabbit.api.JackrabbitNode#rename(String)

in svn r985213

> Provide rename method for nodes
> -------------------------------
>
>                 Key: JCR-2683
>                 URL: https://issues.apache.org/jira/browse/JCR-2683
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-api, jackrabbit-core
>    Affects Versions: 2.2.0
>            Reporter: Michael Dürig
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Currently renaming a node is a nuisance if the node's parent has orderable child nodes: The parents child nodes must be searched for the successor of the node to be moved, the node must be moved to its new name and then ordered before the successor. Furthermore the case where the to be moved node is the last node must be special cased. 
> I thus propose to provide functionality for directly renaming nodes.  

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