Drew McAuliffe wrote:
Here's what's in my velocity.properties file. As I mentioned before, both this and webwork.properties are in my classpath, with webwork.properties referencing the velocity file via the "webwork.velocity.configfile" property. The begin and end markers are not part of the file and are just there to set the contents apart from the rest of the message.
BEGIN # Velocity settings # See the Velocity project (http://jakarta.apache.org/velocity/) for # more info on what settings are available # Also see webwork/default.properties in WebWork if you want # to see what defaults have been set.
#file.resource.loader.path = / file.resource.loader.cache=true
wwfile.resource.loader.cache=true ## specified in seconds wwfile.resource.loader.modificationCheckInterval=5
velocimacro.library.autoreload=true velocimacro.library=webwork.vm,macros/udc.vm,macros/pageset.vm #runtime.log=c:/data/velocity.log END
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Hernandez Sent: Sunday, February 01, 2004 3:41 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Velocity Template caching
i dont know much about velocity but could you post the minimal or recommended velocity.properties file (and where it needs to be, either classpath or WEB-INF dont know) on the wiki and whatever else needs to be done to enable caching of the templates
Drew McAuliffe wrote:
I definitely know that it works, b/c the improvement is pretty noticeable.
Here's what I have: -webworks.properties in classpath -velocity.properties in classpath -webworks.properties includes the following line:
webwork.velocity.configfile=velocity.properties
That last bit might be the key.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hans Prueller
Sent: Sunday, February 01, 2004 3:50 AM
To: [EMAIL PROTECTED]
Subject: AW: [OS-webwork] Velocity Template caching
in my case, it didn't work... i tried to use wwfile.resource.loader.cache = true wwfile.resource.loader.modificationCheckInterval = 10
in webwork.properties AND in a velocity.properties file in classpath..
if I modify a template, the changes are immediately visible. do I need a newer version of WW2 than beta2 ???
hans
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Fernando Martins
Gesendet: Samstag, 31. Jänner 2004 18:59
An: [EMAIL PROTECTED]
Betreff: Re: [OS-webwork] Velocity Template caching
On Saturday 31 January 2004 13:22, Fernando Martins wrote:
I tried this, and it seems to be working.wwfile.resource.loader.cache = true wwfile.resource.loader.modificationCheckInterval = <some_interval>
I don't know if this will work, I'll give a try, and let you know.
So after all is quite easy to turn on velocity template caching in ww2.
One just needs to add these 2 lines to velocity.properties:
wwfile.resource.loader.cache = true wwfile.resource.loader.modificationCheckInterval = <some_interval>
This should speed up things quite a bit, when using File resource templates.
This information should be available in some place in the documentation/wiki.
If some of the core developers be so kind to add it or at least to say where it should be added.
thanks Fernando Martins
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
