[logback-dev] [JIRA] Created: (LBCLASSIC-310) ReconfigureOnChangeFilter should re-use substition properties from initial configuration

Gunnar Wagenknecht (JIRA) noreply-jira at qos.ch
Fri Dec 2 11:17:12 CET 2011

ReconfigureOnChangeFilter should re-use substition properties from initial configuration

                 Key: LBCLASSIC-310
                 URL: http://jira.qos.ch/browse/LBCLASSIC-310
             Project: logback-classic
          Issue Type: Improvement
          Components: joran
    Affects Versions: 0.9.27
            Reporter: Gunnar Wagenknecht
            Assignee: Logback dev list

Logback configuration files are automatically reloaded when {{scan="true"}} is set. This is implemented using {{ReconfigureOnChangeFilter}}. The actually re-configuration happens in {{ReconfiguringThread}} which always creates a new default {{JoranConfigurator}}.

This is works as long as the initial {{JoranConfigurator}} hasn't been extended to support additional substitution properties.

// create our customized configurator
final JoranConfigurator configurator = new JoranConfigurator() {
   protected void addImplicitRules(final Interpreter interpreter) {
      // set some properties for log file substitution
      if (null != instanceLogfileDirectory) {
         interpreter.getInterpretationContext().addSubstitutionProperty("my.property", calculateMyPropertyValue());

It should somehow be possible to inherit the custom substitution properties into the new {{JoranConfigurator}}. Otherwise they are lost on re-configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list