When auto-configuration is preformed it first searches for log4j.xml in the classpath and if it doesn't find it then it searches for log4j.properties in the classpath. Auto-configuration basically only occurs once (I think the only exceptions are different classloaders or repository selectors).
On 1/12/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote:
Jacob Kjome <hoju <at> visi.com> writes: > If none of the above suggestions pan out, have you made sure that > some other log4j.properties or log4j.xml (which would get picked up > in preference to log4j.properties, even if it comes later in the > classpath) isn't in the classpath? So let me make this clear: if you have log4j.properties in a.jar, b.jar, and c.jar, will autoconfiguration performed from each of the jars: 1. load that specific jar's log4j.properties? 2. will the last autoconfiguration overwrite the first one? If yes, would overwriting be prevented by using a special per-jar configuration file, or would that still overwrite the previous configurations? Sorry for bugging you guys. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
