Kent Tong wrote:
In a development environment it's desirable to reload a webapp if any of
its class files has been changed.
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.). 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, when it is
accessed again.
Don't you run tests after changing your apps? ;-)
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 a background scheduler).
I (think I) understand your Wish, but I reckon they way you work
is so unusual that you won't be able to rally much support for it.
In our apps, it's initialisation of the application bean that takes
time, and this happens at first request, not at reload.
Yes, I know about the reload function in the Tomcat manager. But it requires
two manual steps: first, reload the webapp; second, access a page in the
webapp.
Paul Singleton
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
