Hi, It seems that the ClasspathResourceLoader doesn't consider the modificationCheckInterval property. Once the template is cached, it will always remain as "none modified". Please try to set the class.resource.loader.cache property to false.
J -----Ursprüngliche Nachricht----- Von: Vinay_s [mailto:vinayiyenga...@gmail.com] Gesendet: Montag, 24. August 2009 15:35 An: user@velocity.apache.org Betreff: Velocity - Resource Loader Caching Issue Hi Guys, Need help in resolving an issue. My webapp has a singleton VelocityEngine implementation. private static VelocityEngine ve; static{ Properties properties = new Properties(); properties.setProperty("resource.loader", "class"); properties.setProperty("class.resource.loader.class", "org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader"); properties.setProperty("class.resource.loader.cache","true"); properties.setProperty("class.resource.loader.modificationCheckInterval", "1"); ve = new VelocityEngine(); ve.init(properties); } Now using the above ve, i create a new context every time and merge the data values. However, when I change the template, and try to render the data The resource loader is still loading the old template and not picking up the newly saved template. What Could I be doing wrong? Please advise. Thanks, Vinay -- View this message in context: http://www.nabble.com/Velocity---Resource-Loader-Caching-Issue-tp25116178p25116178.html Sent from the Velocity - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
