Paul Singleton paul at jbgb.com writes:
Are you serious?! Our developers rely on Hot Code Replacement to
enable them to continue debugging after changes to program logic,
and only restart if they want/need to or if HCR fails (e.g. because
they added/altered a public member signature etc.).
Christopher Schultz chris at christopherschultz.net writes:
Why not only copy your new WAR file (or classes, etc.) to the deployment
directory when you actually want the webapp to reload?
Creating a WAR file and copying it takes quite a lot of time. So, the
webapp is setup as an exploded
Christopher Schultz chris at christopherschultz.net writes:
I'm suggesting that you only deploy when you need to (even just copying
files into your exploded WAR area). Are you updating your app many times
more often than you want to reload it? Why?
Because the project output folder in Eclipse
Hi,
In a development environment it's desirable to reload a webapp if any of
its class files has been changed. I know about the reloadable flag, but
it will keep reloading the webapp whenever a change is made and slows down
the computer. Instead, I'd like to reload it on demand, ie, when it is
