[
https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-13875:
-------------------------------------
I've committed a fix for 'start' or 'restart' on the module. It seems
we set the state to started, waited for the server to respond the module was up, but then
we didnt set the state after that.
For responding to a server 'restart', the work may be more, and I have to dig
deeper.
Incorrect Module status when starting server/module
---------------------------------------------------
Key: JBIDE-13875
URL:
https://issues.jboss.org/browse/JBIDE-13875
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.1.0.Alpha2
Create and deploy a webapp on an AS or EAP server.
* When the app server is started, the webapp module appears as "stopped", even
though it's started.
* When the server is restarted, The module just says "synchronized"
* When one click "start" on the webapp module, its state stays in
"starting" mode, even though the app is done starting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira