> > I've noticed that Tapestry seems to be somehow caching my templates even > when I rebuild and redeploy my web app. How do I prevent this? It's making > it very difficult to make changes while I debug. >
What version of Tapestry are you using? It's helpful to put that in the subject. Also, what application server are you deploying to? See the recent message "*RE: T5 developing with WTP and TOMCAT*" Also, I ran into a problem that sounds like yours with Tomcat. I used Maven to build the war, dropped it into the webapps folder so that tomcat would auto-deploy the app. Some old templates were still being used, but this wasn't a Tapestry problem. I checked in the folder where tomcat had exploded the war and there were both new and old files mixed in there... I've had no problems using Jetty for debugging, and I'm considering replacing Tomcat with Jetty for production. Josh On 9/5/07, Jean-Philippe Steinmetz <[EMAIL PROTECTED]> wrote: > > > I've noticed that Tapestry seems to be somehow caching my templates even > when I rebuild and redeploy my web app. How do I prevent this? It's making > it very difficult to make changes while I debug. > > > Jean-Philippe Steinmetz > > > > -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox.
