In answer to my previous question, it looks like the modification check interval is specified in seconds. That's what I understood from looking over the velocity docs.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando Martins Sent: Saturday, January 31, 2004 9:59 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Velocity Template caching On Saturday 31 January 2004 13:22, Fernando Martins wrote: > wwfile.resource.loader.cache = true > wwfile.resource.loader.modificationCheckInterval = <some_interval> > > I don't know if this will work, I'll give a try, and let you know. > I tried this, and it seems to be working. So after all is quite easy to turn on velocity template caching in ww2. One just needs to add these 2 lines to velocity.properties: wwfile.resource.loader.cache = true wwfile.resource.loader.modificationCheckInterval = <some_interval> This should speed up things quite a bit, when using File resource templates. This information should be available in some place in the documentation/wiki. If some of the core developers be so kind to add it or at least to say where it should be added. thanks Fernando Martins ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
