to or if HCR fails (e.g. because
they added/altered a public member signature etc.). They would
not be happy with your policy!
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
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.).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kent,
Kent Tong wrote:
John McPeek spambomb at bellsouth.net writes:
If you use eclipse and WTP it does all that for you. Then you can spend
almost 0 time thinking about start/stop/reload stuff.
Thanks for the reply. However, it will reload
directory. What's missing is reload
it on demand.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
it takes quite a lot of time. So, the
webapp is setup as an exploded directory. What's missing is reload
it on demand.
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
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
, 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
accessed again. Is it a desirable feature? It shouldn't be that hard to
implement (invoke the reload logic before any access to the webapp instead
of from
