[Registry-dev] [jira] Closed: (REGISTRY-304) Can not rename and move resource in to new collection.

[Krishantha Samaraweera (JIRA)]

     [ https://wso2.org/jira/browse/REGISTRY-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krishantha Samaraweera closed REGISTRY-304.
-------------------------------------------

         Assignee: Krishantha Samaraweera  (was: Chathura Ekanayake)
    Fix Version/s: 1.1
       Resolution: Won't Fix

Now resource move and copy are two separate functions. User can not move the resource while renaming.

> Can not rename and move resource in to new collection.
> ------------------------------------------------------
>
>                 Key: REGISTRY-304
>                 URL: https://wso2.org/jira/browse/REGISTRY-304
>             Project: WSO2 Registry
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1
>         Environment: WinXP, apache-tomcat-6.0.14,jdk-1_5_0_13,IE 7.0
>            Reporter: Krishantha Samaraweera
>            Assignee: Krishantha Samaraweera
>             Fix For: 1.1
>
>
> How to recreate:
> 1. Login as Admin.
> 2. Add a resource in to root level (r1.txt)
> 3. Then rename the resource as "/c1/c2/c3/r1.txt"
> /c1/c2/c3/ collections will not be created.

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