i think the resources they talk about there are markup resources - wicket only cashes markup and .property files. everything else like CSS and Javascript should not be cached if modified date changed on the file.
-igor On Thu, Nov 4, 2010 at 8:35 AM, Arjun Dhar <[email protected]> wrote: > > Hi, > I'm trying to understand wickets ability to cache and how to optimize of > the deployment mode etc. > > I wanna keep it in production (DEPLOYMENT MODE). However, when a resource is > uploaded (like an image or a CSS) I want the system to allow me to refresh > that particular resource. > > Some of the resources are added via the Wicket Code dynamically and some are > references via the Markup. Is there a difference in how these two are > treated? > > In Reference[2], at the end of the post a guy mentioned about "what about > activating JMX and clearing the cache with it's help" ..that may be cool? > ..or even via a API Call. > > > References: > 1. https://cwiki.apache.org/WICKET/faqs.html#FAQs-Deployment > 2. > http://apache-wicket.1842946.n4.nabble.com/Refresh-resources-in-deployment-mode-td1867352.html > > Thoughts and further reading appreciated! > > Thanks > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Resource-caching-Deployment-Mode-Re-visited-tp3027244p3027244.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
