That's why I asked for more details. Wicket caches the .html templates so they are read just once from the file system. While ResourceSettings.setDefaultCacheDuration is about the Cache related response headers.
You need org.apache.wicket.settings.IMarkupSettings#getMarkupFactory().getMarkupCache().clear(); On Thu, Jan 17, 2013 at 5:58 PM, Tom Norton < [email protected]> wrote: > Last time I checked, wicket caches all resources for each page in > deployment mode. I want to know if there is a way to clear cache without > using ResourceSettings.setDefaultCacheDuration. > > Thanks, > Tom > > > On Thu, Jan 17, 2013 at 10:42 AM, Martin Grigorov <[email protected] > >wrote: > > > Can you be more specific which caches you want to clear ? > > It sounds like you need to clear the cache in the browser. The browser > wont > > make a request to the server if there is a cache for this url. So you > need > > to clear the browser cache, no Wicket involved. > > > > > > On Thu, Jan 17, 2013 at 4:47 PM, Tom Norton < > > [email protected]> wrote: > > > > > Is there a way to clear the HTML cache on demand instead of using > > > expiration timeouts in Wicket 1.5? > > > > > > Thanks, > > > Tom > > > > > > > > > > > -- > > Martin Grigorov > > jWeekend > > Training, Consulting, Development > > http://jWeekend.com <http://jweekend.com/> > > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
