We had a similar problem. Our solution has two parts:
1. Only define the root category in one log4j config file. The others
should not contain a root category.
2. Load the config file containing the root category on startup.
Scott Rogers
----- Original Message -----
From: "Pugh, Eric" <[EMAIL PROTECTED]>
To: "'LOG4J Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Friday, March 23, 2001 9:25 AM
Subject: Category Inheritance Question
> Hi all,
>
> I have an object called Product... In it's constructor I call an init
> method that loads up a log4j_product.prop file...
>
> I am calling this object from multiple other objects...
>
> When i call it from objectA, I want to have it's logging going to
objectA's
> log file.
>
> However, when I call it from objectB, I want it to send it's logging to
> objectB's log file.. Should I pass in what property file it uses? Or,
will
> the category that I definie in my product object automatically pick up the
> properties if they are definied in objectA or B?
>
> Eric
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
