[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-user
Subject:    Re: No	RuntimeConstants.FILE_RESOURCE_LOADER_MODIFICATIONCHECKINTERVAL?
From:       "Geir Magnusson Jr." <geirm () optonline ! net>
Date:       2001-09-27 4:10:05
[Download RAW message or body]

On 9/27/01 12:03 AM, "David Rees" <drees@runt.ebetinc.com> wrote:

> On Wed, Sep 26, 2001 at 10:13:27PM -0400, Geir Magnusson Jr. wrote:
>> 
>> Somewhat intentional.  It's kind of weird.  This is a carryover from when we
>> only had a file loader - this (and "cache") are constants that are general
>> (somewhat) to loaders, so while we could have FILE_RESOURCE_LOADER_CACHE, we
>> should also have JAR_RESOURCE_LOADER_CACHE and
>> DATASOURCE_RESOURCE_LOADER_CACHE, etc...  So I think we just left them off.
>> 
>> Couple this with the fact that you don't have to call the file resource
>> loader 'file' : i.e.
>> 
>> 
>> resource.loader = woogie
>> woogie.resource.loader.class =
>>       org.apache.velocity.runtime.resource.loader.FileResourceLoader
>> woogie.resource.loader.cache = true
>> woogie.resource.loader.modificaationCheckInterval = 10
>> 
>> Is a perfectly legit (although weird) way to do it...
>> 
>> So we just kinda let it go, and made sure things were well and correctly
>> defined in the documentation.
> 
> OK, kinda makes sense now, then.  Does that mean you may be deprecating some
> of those constants in the future?

Maybe.  I guess we can see how people feel.

geir

-- 
Geir Magnusson Jr.     geirm@optonline.net
System and Software Consulting
"They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety." - Benjamin Franklin

[prev in list] [next in list] [prev in thread] [next in thread]