Yes, log4j is only configured once. If you want each jar to have isn't own config then you need to look into repository selectors.
On 1/12/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote:
James Stauffer <stauffer.james <at> gmail.com> writes: > > 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). So in my example, provided the 3 jars are loaded by the same classloader, if the first log4j.xml (log4j.properties) was found in c.jar, then it will be used for a.jar and b.jar, despite those jars having their own config files, right? --------------------------------------------------------------------- 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]
