Hi Trong, I am not sure which scenarios are impacted by this? Changing a template through the admin UI for example? What else? -- P On 2014-04-25 05:53, Trong Tran wrote: > Hi *, > > I see that loading templates impacts a lot to response time. So we would > change to use infinite TTL for TemplateService cache config by default > (it is currently 600s). Because ideally the number of templates are > fixed and they never changes in production mode by default. > > Does anybody see any problem with that ? > > The present PR is https://github.com/gatein/gatein-portal/pull/843 > > -- > *Trong Tran* > /(+84) 983841909 | /trongtt(a)gmail.com <mailto:trongtt@gmail.com> > Twitter: http://twitter.com/trongtt// > > > _______________________________________________ > gatein-dev mailing list > gatein-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/gatein-dev > _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/gatein-dev

Hi Peter, Changing a template through the admin UI should not be the case as it should use TemplateService to manually invalidate the cache. So whatever scenarios are that templates are being changed without manually invalidating corresponding cache are impacted, like changing directly the template system file by an external editor. This is only about changing default configuration for template caching which will be used if the cache system property setting is omitted. If you don't find any impact, I would like to change this in 3.7 and master branches.

WDTY ?

Hi, I see that 3.8.0.Final was tagged last Friday. Could you make branch for it, then we can continue with other stuffs in 3.9 ? Thanks _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/gatein-dev