[jbosstools-issues] [JBoss JIRA] (JBIDE-11509) Starting the AS/EAP when it already has multiple projects deployed

[ https://issues.jboss.org/browse/JBIDE-11509?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11509: ------------------------------------- Considering this is a bug in the app server, I'm not sure what can be done here on the tooling side. I can try to add logic to verify module state after a server starts up, but we have to remember that different app servers have different levels of support for verifying deployment status. For example, the jmx beans in jboss 6 that verify module state seem to be missing (JBIDE-11514). Also, if the deployments are on a remote server, verification will depend entirely on whether their management services are exposed. Otherwise there'll be pretty much nothing I can do to verify the state of modules. Finally, verifying the actual state of all modules may end up slowing down the startup process. This may be a minor concern, really, but it's a possibility worth noting. -- 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