[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8301) Not clear what Start/Stop actually does for remote servers

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-8301: ------------------------------------ You cannot really avoid these actions. Either you want the state to be accurate, in which case commands will be launched and polling will be done to verify the state, or you want non-actions, in which case the 'started' / 'stopped' state is 100% meaningless and irrelevant. You can't have it both ways. Either the state is accurate, and commands get launched, polling done, actions fail, or the state is irrelevant, and there's no verification anything is up or down, and then other actions will fail when the adapter assumes the server is up and tries to execute JMX commands on it. Please tell me if you would prefer actions fail when they are unsuccessful but state is accurate, OR if you'd prefer state be innacurate and start / stop do whatever you want with no verification (and hte possibility of other behaviour errors when the adapter expects functionality to be available and it is not). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira