[dna-issues] [JBoss JIRA] Resolved: (DNA-375) Enhance MoveBranchRequest to take a new name, analogous to how CopyBranchRequest works

Wed Apr 22 04:49:22 EDT 2009

     [ https://jira.jboss.org/jira/browse/DNA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-375.
-------------------------------

    Resolution: Done

Changed the connector API's MoveBranchRequest to have a new desiredName() field, and changed the writable connectors to implement these new semantics.  Also expose this through the Graph API.  Added several tests to the connector unit test framework to test for these additional move behaviors.

> Enhance MoveBranchRequest to take a new name, analogous to how CopyBranchRequest works
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-375
>                 URL: https://jira.jboss.org/jira/browse/DNA-375
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>
> CopyBranchRequest has a desiredNameForCopy that is used to specify the name for the new copy, which may be null if the original name is to be used.  MoveBranchRequest should also have a desiredNewName that, if provided, would also rename the node.
> This change will affect all of the existing connectors that support updates, but it does close a gap in the Graph functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira