struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Nenning (JIRA)" <j...@apache.org>
Subject [jira] [Created] (WW-4267) When devMode is enabled via CustomConfigProvider it is not possible to enable reloading automatically
Date Thu, 02 Jan 2014 08:41:50 GMT
Christoph Nenning created WW-4267:
-------------------------------------

             Summary: When devMode is enabled via CustomConfigProvider it is not possible
to enable reloading automatically
                 Key: WW-4267
                 URL: https://issues.apache.org/jira/browse/WW-4267
             Project: Struts 2
          Issue Type: Bug
          Components: XML Configuration
    Affects Versions: 2.3.16
            Reporter: Christoph Nenning
            Priority: Trivial


When devMode is enbaled the framework used to enable some other debug options per default,
like reloading of config and resources. In 2.3.16 that was changed to be able to have devMode
without all of those other options. The reason for that are performance issues with freemarker
debug options.

A side effect of that is that automatic enablement of reloading does not work anymore when
devMode is enabled via a CustomConfigProvider.

To fix that default settings in default.properties can be outcommented. That way it does not
take effect at runtime but is still present for developers to read the file.

These properties are affected:
- struts.i18n.reload
- struts.configuration.xml.reload
- struts.freemarker.templatesCache
- struts.freemarker.templatesCache.updateDelay




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message