[
https://issues.jboss.org/browse/JBIDE-9707?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-9707:
------------------------------------
Steps to Reproduce:
- EXEC: Create a Web project
- EXEC: Create an AS7 server instance
- EXEC: Web Project : Run As > run on Server (choose the AS7 instance)
- ASSERT: After project start is complete, check the Web App module in the server view has
its state == [Started, Synchronized]
- EXEC: Stop the AS7 server instance
- ASSERT: the Web App module state == [Stopped, Synchronized] <-- Fails, it shows
[Started, Synchronized]
was:
- Create a Web project
- EXEC: Create an AS7 server instance
- EXEC: Web Project : Run As > run on Server (choose the AS7 instance)
- ASSERT: After project start is complete, check the Web App module in the server view has
its state == [Started, Synchronized]
- EXEC: Stop the AS7 server instance
- ASSERT: the Web App module state == [Stopped, Synchronized] <-- Fails, it shows
[Started, Synchronized]
AS7 server adapter: modules states show as [Started, Synchronized]
after stopping the server
--------------------------------------------------------------------------------------------
Key: JBIDE-9707
URL:
https://issues.jboss.org/browse/JBIDE-9707
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.3.0.Beta1
After stopping an AS7, its deployed modules are still displayed as [Started,
Synchronized].
Possibly related to JBIDE-9050 (or not).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira