I'm looking for some guidance on either a conf change, rearchitecting, or custom class I can implement to more efficient cache parsed versions of *shared* velocity templates.
I have implemented two velocity context loaders... 1. a per-customer set of files and 2. system-provided files The idea behind this layering is that each customer will automatically have standard files that the system provides, and they just need to dump in a copy of the file into their set of files to effectively override and customize that template. This all works well. My challenge is how to efficiently have velocity parse and cache those shared files. AFAICT, the system provided files are getting parsed and cached per customer by velocity, i.e., velocity is cacheing templates based on the resource location, not the resource data/loader that's providing it. I don't see any way in the API to do what I'm trying to do, so if anybody can give me suggestions, that'd be great. I've implemented a custom ResourceCache, ContextLoaders, so am comfortable extending the API as needed. -- 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]
