It sounds like you have a good user story. Thoughts from Ralph? Gary
<div>-------- Original message --------</div><div>From: Remko Popma <remko.po...@gmail.com> </div><div>Date:06/15/2014 08:33 (GMT-05:00) </div><div>To: Log4J Developers List <log4j-dev@logging.apache.org> </div><div>Subject: LoggerContext config location </div><div> </div>I would like the ability to get the ConfigurationSource from the LoggerContext in order to fix LOG4J2-539. Currently LoggerContext has a field configLocation:URI, but this field may (or may not) be initialized when the LoggerContext is constructed, and is not updated when it is reconfigured. In fact, all reconfiguring uses inner class ConfigurationFactory.ConfigurationSource. I would like to make the following changes: * make ConfigurationFactory.ConfigurationSource a top-level class * add method getConfigurationSource to the Configuration interface * remove field configLocation (and getter/setter) from LoggerContext Client code that needs LoggerContext.getConfigLocation() can instead call LoggerContext.getConfiguration().getConfigurationSource(). This is more reliable than getConfigLocation() as this URI is often null and may not be in sync with the LoggerContext's Configuration after a reconfigure. Thoughts?
