Mailing-List: contact log4j-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: calling DOMConfigurator.configureAndWatch()  2 times 
Date: Wed, 13 Aug 2003 09:17:52 -0400
Message-ID: <9C5166762F311146951505C6790A9CF8346486@US-VS1.corp.mpi.com>
Thread-Topic: calling DOMConfigurator.configureAndWatch()  2 times 
Thread-Index: AcNha0Z0RyBRaG8oRPyAcJqQy62P2gAMTZQw
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Log4J Users List" <log4j-user@jakarta.apache.org>


Howdy,

>What should happen if the configureAndWatch() function is called twic=
e?
>Are the previous settings erased? Are they accumulated ?

It wouldn't be that hard to simply test this and see what happens ;)

But looking at the code, you see:

- configureAndWatch always creates a new XMLWatchdog, so you will have=

two XMLWatchdogs watching over the file.  

- Each XMLWatchdog would call DOMConfigurator#doConfigure(filename,
repository) when the file changes, so this method will get called twic=
e.
So this is extra overhead that should be avoided if possible.

- The configuration file will get parsed again with a new parser

- Parsing will replace where found and add where not found.  So if
there's already a logger for class, for example, it will be retrieved =
if
it exists and reconfigured, or a new one will be created if one doesn'=
t
exist.

You can walk through the rest of DOMConfigurator if you feel like it ;=
)
This is one issue where the test is easy so I wouldn't even spend time=

looking at the code ;)

Yoav Shapira


This e-mail, including any attachments, is a confidential business com=
munication, and may contain information that is confidential, propriet=
ary and/or privileged.  This e-mail is intended only for the individua=
l(s) to whom it is addressed, and may not be saved, copied, printed, d=
isclosed or used by anyone else.  If you are not the(an) intended reci=
pient, please immediately delete this e-mail from your computer system=
 and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org