[
https://issues.jboss.org/browse/JBIDE-11514?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11514.
---------------------------------
Resolution: Done
Made another commit here. all better. Seeems the standalone war example worked... but
nested war inside ear was what failed. Uses same mbean as standalone now. (In earlier
versions, nested inside ear used different mbean)
AS6 run on server for war or ear-inside-war does not load browser
fast
----------------------------------------------------------------------
Key: JBIDE-11514
URL:
https://issues.jboss.org/browse/JBIDE-11514
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
AS6 does not seem to have the mbeans as5 and below do for determining if a module is
started or not. This means that attempts to poll via jmx to decide when to open the
browser take the full timeout of 20 seconds.
Without a way to decide if the module is started or not, we have to hard-code a delay
time. There is no easy answer here. If we go too quickly, the user will get 404. If we
delay too long, the user will wait a long time to see the change.
--
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