Assuming this is a regular production website, if you're just
changing the HTML and/or .page file, you can make the changes then
either restart Tomcat or reload the app within Tomcat. Be aware that
if the app came from a WAR file that deploying a newer WAR file will
overwrite your changes.
Tapestry defaults to reading the HTML once and caching the result,
which is why you need to restart (Tomcat) or reload (the app). As far
as I know, the reset service won't erase Tapestry's cache, so it's
not really an option.
Developers typically run with this caching disabled and can make live
changes to the pages, at the expense of decreased performance.
...Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
