Hi! Thanks for your reply. I guess didn't give too much a reason to why this is a problem for me and our software project. Our project has a central properties file consisting of two parts, a default part with general properties (located in the jar) and specified part sent with execution of the program. Most of the Log4J properties used in our system will be in the default properties, and ignored by Log4J 1.1.3. I'm sending our properties object to the PropertyConfigurator.configure(Properties) method, which in turn calls the "buggy" PropertySetter.setProperties(...) method.
Hope this helps to understand why this was a problem for me. :) And thanks for applying the patch. -- Georg Lundesgaard enonic.com PS: I was unsure of which list to post to, the "Contant us"-page said I should post to the user list, but something told me (a hunch?:) that I should send it to the dev list. Sorry for making too much of a noise. :) -----Original Message----- From: Ceki Gulcu [mailto:[EMAIL PROTECTED]] Sent: 16. november 2001 13:05 To: Log4J Developers List Subject: Re: BUG: PropertySetter ignores default properties in the java.util.Properties object sent to setProperties(java.util.Properties, String) Your patch seems very reasonable. However, I wonder under what circumstances in really makes a difference. I don't think the default properties for the propperties parameter are set anywhere in log4j code before invoking PropertySetter.setProperties(Properties, String). Are you setting the default properties yourself? Regards, Ceki ps: I will apply your patch even tough I don't see its utility but it can't do harm. By the way, avoid cross posting to multiple mailing lists. At 11:55 16.11.2001 +0100, Georg Lundesgaard wrote: [snip] - bug description -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
