[Registry-dev] [jira] Closed: (REGISTRY-192) Visioning not happening for collection update

Krishantha Samaraweera (JIRA) jira at wso2.org
Fri Feb 29 04:45:44 PST 2008


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

Krishantha Samaraweera closed REGISTRY-192.
-------------------------------------------

    Assignee: Krishantha Samaraweera  (was: Chathura Ekanayake)

dev comments accepted.

> Visioning not happening for collection update
> ---------------------------------------------
>
>                 Key: REGISTRY-192
>                 URL: https://wso2.org/jira/browse/REGISTRY-192
>             Project: WSO2 Registry
>          Issue Type: Bug
>          Components: versioning
>    Affects Versions: SNAPSHOT
>         Environment: Ubuntu 7.10, JDK 1.5.0_08, tomcat 6.0.14, Firefox/2.0.0.8
>            Reporter: Krishantha Samaraweera
>            Assignee: Krishantha Samaraweera
>
> How to recreate:
> 1. login as admin.
> 2. add a new collection c1 in to root level.
> 3. again add the same collection c1 in to root level.
> c1 remain in v1 event though user added same collection several times.

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