[Carbon-dev] [jira] Updated: (CARBON-4777) Rampart re-engaged to the service after restarting the server

Ruwan Linton (JIRA) jira at wso2.org
Thu Jul 2 08:37:00 PDT 2009

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

Ruwan Linton updated CARBON-4777:

    Fix Version/s: Future
         Severity: Critical  (was: Major)
         Priority: Normal  (was: High)

This is out of the scope of this release now because we are planning to code freeze now and this is not a blocker for the release.

> Rampart re-engaged to the service after restarting the server
> -------------------------------------------------------------
>                 Key: CARBON-4777
>                 URL: https://wso2.org/jira/browse/CARBON-4777
>             Project: WSO2 Carbon
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 2.0 RC5
>         Environment: winxp, jdk16, FF3
>            Reporter: Charitha Kankanamge
>            Assignee: Nandana Mihindukulasooriya
>             Fix For: Future
> Steps to reproduce:
> ===============
> 1. Select a service and assign UT scenario
> 2. Disable security 
> 3. Restart server
> 4. Go to service dashboard and click on modules
> You will see that rampart is shown as an engaged module.

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 Carbon-dev mailing list