What I'd like is the resource manager to check the customized template folder first before turning to the default template folder, and ideally still use a cached version for that. Is the only way to do this to write my own ResourceManager implementation, or is there another way to do this?
Which loaders are you using, and how are you configuring them? I
think one FileResourceLoader with multiple paths should do the trick. (Haven't tried, though)
resource.loader=file1,file2 file1.resource.loader.class=org.apache.velocity.runtime.resource.loader.FileResourceLoader file1.resource.loader.path=foo file1.resource.loader.cache=true file2.resource.loader.class=org.apache.velocity.runtime.resource.loader.FileResourceLoader file2.resource.loader.path=bar file2.resource.loader.cache=true
Put a template into "bar" and have Velocity try to render that template. Then put a template with the same name into the "foo" directory, and you'll continue to get a copy of the "bar" version. If you restart Velocity, you'll then see the "foo" version since that appears earlier in the resource loader.
I guess you're saying that the file loader has this ability built-in, but I'm using a mixture of resource loaders and am using the multiple loader feature, so I need the resource manager to handle this.
Again, it seems like I need my own ResourceManager impl, but just wondering if anybody hit this before, had a better suggestion, or a planned work around.
-- Serge Knystautas Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
