logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Moore <jim.mo...@veritas.com>
Subject RE: Difference in using BasicConfigurator v.s. DOMCOnfigurator
Date Thu, 01 Mar 2001 16:23:05 GMT
The log4j.configuration property is to provide a configuration file other
than the default.  The default is log4j.properties (anything else is not the
default).  So if you want it to use something other than the default, you
have to provide that property.  BasicConfigurator then takes a guess at
whether to use PropertyConfigurator or DOMConfigurator based upon the
extension of the file.

log4j.configuration expects a URL.  When using the PropertyConfigurator you
can leave out the protocol (the "file:" part), but not with DOMConfigurator
(or at least that's how it is in 1.04).  I don't know why -- I just know if
I include the "file:" it works and if I leave it off it doesn't work.

-Jim Moore

-----Original Message-----
From: John Carnahan [mailto:carnahan@protos.lifesci.ucla.edu]
Sent: Thursday, March 01, 2001 10:52 AM
To: LOG4J Users Mailing List
Subject: Re: Difference in using BasicConfigurator v.s. DOMCOnfigurator


Why is this so? Assuming the file is local, Class.getResource will 
return a URL with prefix 'file' that should work regardless of whether 
the file is a properties file or xml. As long as either is somewhere in 
the classpath this works great. The only question that would remain is 
precedence if both are found.


> You have to provide what file to use as a system property. For example:
> java -Dlog4j.configuration=file:log4j.xml MyProgram
> -Jim Moore
> -----Original Message-----
> From: Rouwendaal, Fernand [mailto:Fernand_Rouwendaal@nl.compuware.com]
> Sent: Thursday, March 01, 2001 3:17 AM
> To: 'log4j-user@jakarta.apache.org'
> Subject: Difference in using BasicConfigurator v.s. DOMCOnfigurator
> Hi,
> When using the BasicConfigurator, you can make use of a very handy
> The configuration file log4j.properties is searched for in the classpath.
> Benefit: In your code, you never have to specify the location hardcoded.
> When using the DOMConfigurator, I cannot make this mechanism to work. Am I
> doing something wrong, or is this feature unsupported for DOMConfigurators
> 	- Fernand.

View raw message