Faulty services are not removed from the 'Available Services' list even if user 
removes the archive file from the ..\WEB-INF\services directory
-----------------------------------------------------------------------------------------------------------------------------------------------

                 Key: AXIS2-1295
                 URL: http://issues.apache.org/jira/browse/AXIS2-1295
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.1
         Environment: Windows XP, jdk1.5.0_08, Maven 1.0.2, Mozilla Firefox 
1.5.0.6
            Reporter: Charitha Kankanamge
            Priority: Minor


Faulty services are displayed in the 'Available Services' list even if the user 
removes them from ..\WEB-INF\services directory. 
System lists down these services until the tomcat server is restarted. 

Steps to reproduce:
===================
1. Create a faulty *.aar file
2. Log in to Axis2 administration console and click on 'Upload Services' link 
in the left pane
3. Browse for the faulty service archive and upload it
4. Click on 'Available Services' link
5. The uploaded service archive will be listed under 'Faulty Services'
6. Navigate to the %tomcathome%\webapps\axis2\WEB-INF\services directory and 
remove the faulty *.aar file
7. Refresh the administration console and check the 'Available Services' list

Actual Result:
=============
Faulty service is still displayed in the 'Available Services' list.

Expected Result:
================
Faulty service should be removed from the 'Available Services' list when user 
removes the archive file from the ..\WEB-INF\services directory.



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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to