Howdy, >1) log4j 1.2.8 PropertyConfigurator & DOMConfigurator both have a small bug >in the void doConfigure(URL url, LoggerRepository repository) methods. >They open a stream on the URL, but do not close it. This means the file >cannot be edited while the application is running because log4j has it >locked. This is easy to fix by closing the stream when log4j has finished >reading it.
Does this break configureAndWatch? >2) Added a new method to LogManager called refreshConfiguration(). This >method will call a newly modified Hierarchy.resetConfiguration. The old >signature was resetConfiguration() and the new one is >resetConfiguration(boolean warnNoEmit). If the parameter is true, log4j >will emit a "Please initialize the log4j system properly." message if any >thread attempts to log before the configuration is reloaded. If false, the >message will never be output. The LogManager.refreshConfiguration() will >then re-load the configuration file that was used when the app first >started. This seems like too big a change for a point release (e.g. 1.2.9), but maybe we should consider it for 1.3. Comments? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
