The JVM cache switch has actually been a bit of a problem for me. Our site (and that of our customers) is vitually hosted. Thus, there is *one* JVM, so I would prefer to handle this at the application.
Also, since 'cache-off' is the intended production setting, how do I add or modify a page on a production site? Could there be some type of administrative interface that would allow me to add a new page or reload an existing page or component on a running site? The reset service sounds to me to be the equivelent of restarting the app - fairly drastic if all I want to do is change some text or add an image. Eric Everman Quoting Geoff Longman <[EMAIL PROTECTED]>: > RE: [Tapestry-developer] Refreshing ala .jsp styleIn older versions > of Tapestry, I don't believe this was possible as specs and templates > had to sit in the classpath. > > Since more recent versions allow templates and specs outside of the > claspath, I dunno if the ways things works has changed to be more > ".jsp" like. > > Howard? ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
