Hi Arthur, I am not sure the problem is your Magnolia Cache. On the author system, the cache is normally disabled anyway. Are your problems occurring only on the public system, or also on the author system? If your templates are not refreshing on the author system as well, the problem is almost certainly not with Magnolia's cache.
Instead, the problem is going to be with the way Tomcat (or possibly your development environment) is setup - it's probably only compiling your JSP pages once, and not detecting your changes afterwards. There are various settings in tomcat to influence this, take a look in the tomcat configuration docs. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Arthur Oysgelt (via Magnolia Forums) Gesendet: Dienstag, 29. Jänner 2013 17:49 An: Magnolia User List Betreff: [magnolia-user] Re: Disable Cache What really makes this situation suck is that this means that on every resource change, i.e. JSP, we need to restart the Tomcat - which is obviously not great for development turnaround. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=f09c563a-3bdb-4757-8b70-4def3d9f097f ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
