| 1. |
I Have To Restart My Application To Pick Up Changes To Specifications And Templates, How Can I Avoid This? |
|
Answer» Start your servlet container with the JVM system parameter org.apache.tapestry.disable-caching set to true, i.e., -Dorg.apache.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 persistent server-side state CORRECTLY. Start your servlet container with the JVM system parameter org.apache.tapestry.disable-caching set to true, i.e., -Dorg.apache.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 persistent server-side state correctly. |
|