1

I have a Dynamic Web Project on eclipse and Tomcat 7 as the server (using within eclipse). After doing 'Run on Server' on the project, it gets deployed and runs on the browser. However, any changes made to the css/js/html/jsp files do get published automatically on save, however doesn't get reflected on the browser without reload. Is there any way to make changes visible on the browser without any reload?

user3376259
  • 51
  • 1
  • 3
  • Sounds like a job for scripting (javascript, etc) ? – EyeOfTheHawks May 21 '14 at 20:53
  • Assuming the final production version of the app will have to worry about these kind of changes...which would be unusual. – nitind May 21 '14 at 21:20
  • I am hitting the same problem, I have to restart the server to see my changes to JS files which is very annoying because it slows down development tremendously – whitestryder Sep 03 '15 at 18:07

1 Answers1

0

For me the problem appears to be fixed by removing the "antiResourceLocking=true" attribute from the Tomcat "context.xml" element.

This is consistent with this post

I'm still trying to determine why Eclipse WTP decides to put this attribute in there in some situations and not others. I have other webapps that are run in Eclipse in the same way and they don't have that attribute set.

Community
  • 1
  • 1
whitestryder
  • 451
  • 5
  • 10
  • Ok, I figured out why Eclipse WTP decides to use the "antiResourceLocking="true". It actually doesn't decide, it just uses the "context.xml" from the Tomcat installation files that you point your server at in Eclipse. I had two different version of Tomcat installed and one had: '' and the other had '' in the conf/context.xml. So the final solution to the problem was to make sure that the Tomcat installation conf/context.xml did NOT have the "antiResourceLocking" attribute set to "true". – whitestryder Sep 03 '15 at 21:53