You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/12/20 03:54:54 UTC
[Jakarta Tapestry Wiki] Updated: ClearingPersistentProperties
Date: 2004-12-19T18:54:53
Editor: SteveByrne <sb...@dorado.com>
Wiki: Jakarta Tapestry Wiki
Page: ClearingPersistentProperties
URL: http://wiki.apache.org/jakarta-tapestry/ClearingPersistentProperties
minto grammar correction
Change Log:
------------------------------------------------------------------------------
@@ -3,7 +3,7 @@
Firstly, using persistent properties on many pages can result in the server memory storage requirements growing unacceptably thus limiting scalability of the application. Secondly, there is a risk of left over state incorrectly being utilised therefore causing undesired behaviour. Thus often you would want to clear the persistent properties once you have finished using a page.
-The tapestry engine ([http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IEngine.html IEngine]) manages the resources and thus provides the mechanism to clear the persistent properties. Normal an action has been triggered and a listener is performing its task, the last step is to cycle to the next page. Just before cycling to the page call the following method.
+The tapestry engine ([http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/IEngine.html IEngine]) manages the resources and thus provides the mechanism to clear the persistent properties. Normally when an action has been triggered and a listener is performing its task, the last step is to cycle to the next page. Just before cycling to the page call the following method.
{{{
this.getEngine().forgetPage(this.getPageName());
}}}
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org