[
https://issues.jboss.org/browse/JBIDE-16866?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-16866:
-------------------------------------
Checked latest fix works ok.
I believe we can still do better, but that's now in the hands of [~xcoulon] :
LiveReload takes 500ms to refresh the browser, that's noticeable. It would be awesome
if we could improve that, but that's the subject for another JIRA
Publishing on AS7/wf servers too slow, does not need to mess with
deployment scanners
-------------------------------------------------------------------------------------
Key: JBIDE-16866
URL:
https://issues.jboss.org/browse/JBIDE-16866
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: respin-a
Fix For: 4.2.0.Beta1
Publishing a single file on WF8 takes at least 2 to 3 seconds before LiveReload refreshes
the browser (I experienced worse turnarounds during EclipseCon demos):
http://screencast.com/t/kQj2kXev3Gyf
If you manually modify the file in the deployment directory on the server, changes are
picked much faster (< 1sec), so it means the whole publishing part within eclipse takes
a tremendous amount of time.
Every time a file is saved in the workspace, the following line shows up in the server
log :
{quote}
INFO [org.jboss.as.server.deployment.scanner] (management-handler-thread - 12)
JBAS015012: Started FileSystemDeploymentService for directory
D:\Dev\servers\wildfly-8.0.0.Final\standalone\deployments
{quote}
This service invocation (which takes at least 1 sec to show up in the log) should be
invoked only once, during server startup, instead of every time a file is published
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira