Oh, thanks a lot for reminding me. In the developer guide, I find the velocity properties that I am looking for:
file.resource.loader.cache = false file.resource.loader.modificationCheckInterval = 2 Thank you very much! bluejoe 2008-11-26 ----- Original Message ----- From: "Nathan Bubna" <[EMAIL PROTECTED]> To: "Velocity Users List" <[email protected]> Sent: Wednesday, November 26, 2008 12:40 AM Subject: Re: question on Template Cache > I'm neither a Dr. nor the only person on this list. Just ask your > questions, no need to address them to one specific person. > > And yes, Velocity does have built in support for caching templates. > This is discussed in the documentation. > > On Mon, Nov 24, 2008 at 10:39 PM, bluejoe <[EMAIL PROTECTED]> wrote: >> Dear Dr. Nathan, >> >> I am very sorry to come up with a new question and have to bother you >> again. >> >> I find the method 'Velocity.getTemplate()' costs much time, especially >> when the template file is very large and complex. To avoid such long time >> cost, I have to store all compiled template objects in memory, e.g. using a >> HashMap. And when the source template files are modified, I have to do more >> to let the cached templates to be reloaded. >> >> I wonder if there is easier method to implement my idea. Can Velocity >> store and reload compiled template in files? Or it contains a built-in >> template cache manager? I need your suggestion. >> >> Many thanks! >> >> bluejoe >> 2008-11-24 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
