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

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596223#comment-12596223 ] 

Max Rydahl Andersen commented on JBIDE-8301:
--------------------------------------------

I have no idea why you think there needs to be a command executed for the state to be correct when it says "started".

I prefer that I have an option to say "do not execute any start/stop commands for this server - just assume it is running and if you can let me know nicely if the server is running or not".

The usecase being I simply want to deploy to an *already* running server - *no* commands should be executed at neither start or stop.



> Not clear what Start/Stop actually does for remote servers
> ----------------------------------------------------------
>
>                 Key: JBIDE-8301
>                 URL: https://issues.jboss.org/browse/JBIDE-8301
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>            Priority: Critical
>             Fix For: 3.2.1
>
>
> when starting/stopping remote servers its not really clear what is going on - i.e. what is the semantics when stopping  a server that were already running when started ?
> Does it execute a command or does it just disconnect ?
> For example right now when I try and stop a server it keeps coming back saying "Server jboss-eap remote failed to stop." and it still says "Started". How do I actually make the server adapter think the server has stopped so it doesn't keep deploying to it withuot having to restart eclipse.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira