[wsas-java-dev] [jira] Closed: (WSAS-517) Control operations are removed when WSAS is restarted

Charitha Kankanamge (JIRA) jira at wso2.org
Thu Sep 13 10:18:48 PDT 2007


     [ http://www.wso2.org/jira/browse/WSAS-517?page=all ]

Charitha Kankanamge closed WSAS-517.
------------------------------------


Verified in WSAS-2.1-RC3 and closed the bug.

> Control operations are removed when WSAS is restarted
> -----------------------------------------------------
>
>                 Key: WSAS-517
>                 URL: http://www.wso2.org/jira/browse/WSAS-517
>             Project: WSO2 WSAS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1-RC2
>            Reporter: Charitha Kankanamge
>         Assigned To: Saminda Wishwajith Abeyruwan 
>            Priority: Blocker
>
> Control operations disappear when restarting WSAS. 
> Steps to reproduce:
> ===============
> 1. Deploy a service engaging sandesha module at service level (Module ref="sandesha2"/>
> 2. Restart WSAS
> 3. Go to 'Manage service operations' page
> 4. control operations are not displayed in the page, however the module is shown as it is engaged to the service 

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

        




More information about the Wsas-java-dev mailing list