[jbosstools-issues] [JBoss JIRA] (JBIDE-10030) Block Browser until Server is Up

[Max Rydahl Andersen (Commented) (JIRA)]

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

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

Not the same I saw in code and my tests.

It waits by pinging the server and before the server this ping errors with a connection error and then the browser was shown too early.

When server is running it checks if the module is deployed, and if it is we open the browser - that should be more or less instantly with no wait.

                
> Block Browser until Server is Up
> --------------------------------
>
>                 Key: JBIDE-10030
>                 URL: https://issues.jboss.org/browse/JBIDE-10030
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M3
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.3.0.M5
>
>
> If you choose "Run As->Run on Server" on a project in eclipse, you'll get your browser pointing to an 404 "Not found" in many cases. This is caused by the browser not waiting until the app server finished deploying and starting the application. 

--
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