[
https://wso2.org/jira/browse/REGISTRY-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved REGISTRY-169.
----------------------------------------
Resolution: Fixed
Fixed the issue in most appropriated way
> Renamed files can be restored.
> ------------------------------
>
> Key: REGISTRY-169
> URL: https://wso2.org/jira/browse/REGISTRY-169
> Project: WSO2 Registry
> Issue Type: Bug
> Components: core
> Affects Versions: SNAPSHOT
> Environment: WinXP, apache-tomcat-6.0.14,jdk-1_5_0_13,IE 7.0
> Reporter: Krishantha Samaraweera
> Assignee: Chathura Ekanayake
> Attachments: renamed_files.JPG
>
>
> How to recreate:
> 1. login as admin.
> 2. add collection /c1/c2
> 3. add a resource r1 to /c1/c2
> 4. rename the resource /c1/c2/r1 as /c1/c2/r12
> 5. go to c2 versions pages.
> 6. check the details of c2 version 3
> Both r1 and r12 resources are displaying under version page. so if I restore
> that version. both the files will get restored.
--
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
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
