First of all I have to ask: why won't you store a template in a relational database?
One word: overkill. Since the database is already a bottleneck in most applications, I try to relieve the stress as much as possible. Usually putting templates (which are used on every request) into the database leads to bad performance. I think velocity templates are cached in memory, so it's probably fine to store them anywhere you want.
But, you'd cache the templates even if they were persistently stored in a database...
I guess it depends on the situation. For us it's the logical thing to do since we have all configuration and object model in a database, and for us the *modified* templates are definitely configuration. So, we'd actually have to do some hacking in order to not store the templates in a database, because that's the natural way to do it.
/Rickard
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
