geirm 01/02/16 06:39:38
Modified: docs developer-guide.html
Log:
xml follower
Revision Changes Path
1.18 +7 -1 jakarta-velocity/docs/developer-guide.html
Index: developer-guide.html
===================================================================
RCS file: /home/cvs/jakarta-velocity/docs/developer-guide.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- developer-guide.html 2001/02/14 23:16:58 1.17
+++ developer-guide.html 2001/02/16 14:39:36 1.18
@@ -636,10 +636,16 @@
<P align="justify">
<CODE><FONT face="courier, monospaced">resource.loader.1.cache =
false</FONT></CODE><BR>
Controls caching of the templates in the loader. Default is false, to make life
easy for development and debugging. This should
-be set to true for production deployment.
+be set to true for production deployment. When 'true', the <CODE><FONT
face="courier, monospaced">modificationCheckInterval</FONT></CODE> property applies.
This allows for the efficiency
+of caching, with the convenience of controlled reloads - useful in a hosted or ISP
environment where templates can be modifed frequently and
+bouncing the application or servlet engine is not desired or permitted.
</P>
<P align="justify">
<CODE><FONT face="courier, monospaced">resource.loader.1.modificationCheckInterval
= 2</FONT></CODE><BR>
+This is the number of seconds between modification checks when caching is turned
on. When this is an integer > 0, this represents the
+number of seconds between checks to see if the template was modified. If the
template has been modified since last check, then it is reloaded and reparsed.
Otherwise nothing is done. When <= 0, no modification checks will take place, and
assuming
+that the property <CODE><FONT face="courier, monospaced">cache</FONT></CODE>
(above) is true, once a template is loaded and parsed the first time it is used,
+it will not be checked or reloaded after that until the application or servlet
engine is restarted.
</P>
<B>Velocimacro</B>