geirm 01/02/16 06:39:05
Modified: xdocs developer-guide.xml
Log:
Added more detail and notes regarding the .cache and .modificationCheckInterval
properties for resource loaders.
Revision Changes Path
1.13 +7 -1 jakarta-velocity/xdocs/developer-guide.xml
Index: developer-guide.xml
===================================================================
RCS file: /home/cvs/jakarta-velocity/xdocs/developer-guide.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- developer-guide.xml 2001/02/14 23:13:00 1.12
+++ developer-guide.xml 2001/02/16 14:39:03 1.13
@@ -624,10 +624,16 @@
<p>
<code>resource.loader.1.cache = false</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>modificationCheckInterval</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>
<code>resource.loader.1.modificationCheckInterval = 2</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>cache</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>
<strong>Velocimacro</strong>
