[Registry-dev] [jira] Updated: (REGISTRY-230) Can not access to collections created with forward slash '/' in the beginning.

Krishantha Samaraweera (JIRA) jira at wso2.org
Wed Jun 4 05:09:40 PDT 2008


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

Krishantha Samaraweera updated REGISTRY-230:
--------------------------------------------

    Assignee: Chanaka Jayasena  (was: Chathura Ekanayake)
    Priority: Blocker  (was: Minor)

Now I can access to the collections.But additional forward slash is being displaying in the resource path. Better to fix this before 1.1 release.

> Can not access to collections created with  forward slash '/' in the beginning.
> -------------------------------------------------------------------------------
>
>                 Key: REGISTRY-230
>                 URL: https://wso2.org/jira/browse/REGISTRY-230
>             Project: WSO2 Registry
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0
>         Environment: Ubuntu 7.10, JDK 1.5.0_08, tomcat 6.0.14, Firefox/2.0.0.8
>            Reporter: Krishantha Samaraweera
>            Assignee: Chanaka Jayasena
>            Priority: Blocker
>         Attachments: collection_added.png
>
>
> How to recreate:
> 1. login as admin.
> 2. go to root level.
> 3. Press add collection button.
> 4. add collections "/c1/c2/c3" in to collection name input field.
> 5. press "Add" button.
> Now try to go to the collection c1 by clicking the collection name." <!-- Page resource path prints he" text will get appeared. If you check the added collection from recent activity search you will notice that resource path is displaying as //c1/c2/c3, one additional forward slash has appened to the resource path.

-- 
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

        



More information about the Registry-dev mailing list