Currently the servlet that reads the configuration (ConfigServlet) caches some of the values that are returned on the query, for example the .properties with the translation strings.
During trainings it is quite annoying to reboot tomcat each time a string is changed. It is also not clear in which cases tomcat has to be rebooted.
Proposed implementation is to set a "configcache" Environment variable that, when false, makes the servlet not cache anything and scan the folders for each query; and when false or not present, will cache everything. That var could be loaded in the servletContext at startup.
fergonco
commented
10 years ago
Currently the servlet that reads the configuration (ConfigServlet) caches some of the values that are returned on the query, for example the .properties with the translation strings.
During trainings it is quite annoying to reboot tomcat each time a string is changed. It is also not clear in which cases tomcat has to be rebooted.
Proposed implementation is to set a "configcache" Environment variable that, when false, makes the servlet not cache anything and scan the folders for each query; and when false or not present, will cache everything. That var could be loaded in the servletContext at startup.