A Closer Look at Simple Components in Apache Tapestry - How to disable caching (Page 4 of 4 )
Tapestry strives to be as efficient as possible, so it caches page templates and specifications in order not to reload them every time when they are needed. This is a very useful behavior in a production application; however, during development it can become annoying, as we might not immediately see the changes we have just made to the page.
Thankfully, there is a way to ask Tapestry not to cache any pages in our development environment.
In NetBeans, click on the Tools menu and then choose Server Manager. In the Server Manager dialog, choose the Platform tab and then enter into the VM Options text box the following option:
-Dorg.apache.tapestry.disable-caching=true
The result should look like this:
Close the dialog, and that’s it. If however Tomcat was running when you applied the setting, you will need to restart Tomcat.
To do this, click on the Runtime tab on the left side of NetBeans IDE and expand the Servers node to see the Bundled Tomcat node:
Right click on the Bundled Tomcat node and choose Restart. As simple as that.
What comes next
In the next part of this tutorial I will explain in more detail how properties of the page class can be defined in Tapestry and when one way is more preferable than the other.
Next we are going to have a more detailed look at the listener methods as there are three ways to write them.
It might also be useful for the future to get familiar with the two ways of submitting the form.
Finally, we shall complete the GuessTheWord project and become familiar along the way with If, Else and PageLink components.
See you in the next article then.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
