[
https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-21467:
---------------------------------------
[~jrichter1],
There's something I cannot reproduce when reading the issue description: if the server
is stopped, the "Open with LiveReload" command on the server module (eg, a
sample application deployed on WildFly) is disabled. So how can you invoke it. Also, can
you clarify when/how you have the 'Unable to open module ...' message ?
Quick access 'open via livereload' with stopped application
server is misbehaving
---------------------------------------------------------------------------------
Key: JBIDE-21467
URL:
https://issues.jboss.org/browse/JBIDE-21467
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.3.1.Beta2
Reporter: Jan Richter
Assignee: Xavier Coulon
Add a project to a stopped application server using the server's add/remove option.
This adds the project to server without starting it up. Then you can select the newly
added server module and use the quick access to 'Show in web browser via
livereload'.
If you have a livereload server running, it says 'Unable to open module ...'. But
if no livereload server is running, it will create/start one and then leave you with a
running livereload server and a stopped application server. It produces no immediate
error/warning.
It does however add this entry to the error log:
{noformat}
Problems occurred when invoking code from plug-in:
"org.jboss.tools.livereload.ui".
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:4491)
at org.eclipse.swt.SWT.error(SWT.java:4406)
at org.eclipse.swt.SWT.error(SWT.java:4377)
at org.eclipse.swt.widgets.Display.error(Display.java:1186)
at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
at
org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
at
org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
at
org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
at
org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)