Re: [Tapestry-developer] [Tapestry-developer]Tapestry could not auto-refresh

[detlef schulze]

Excerpt from the FAQ section:   I have to restart my application to pick up changes to specifications and templates, how can I avoid this? Start your servlet container with the JVM system parameter net.sf.tapestry.disable-caching set to true, i.e., -Dnet.sf.tapestry.disable-caching=true. Tapestry will discard cached specifications and templates after each request. You application will run a bit slower, but changes to templates and specifications will show up immediately. This also tests that you are persisting server-side state correctly.     ----- Original Message ----- From: airwing To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 2:50 PM Subject: [Tapestry-developer] [Tapestry-developer]Tapestry could not auto-refresh Tapestry could not refresh after I modify *.html. I had to restart app server to enable the modified feature. This is a big bug if I am not wrong. any one could give some advice?