On May 5, 2009, at 5:17 PM, Martin Fernau wrote:
Hello,
I've a problem adding a Filter at runtime.
My log4j.properties looks like this:
--- cut
log4j.rootLogger=info, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
---
Hello Luca,
you can solve this via a system property.
When you specify your log file like this:
log4j.appender.LOGFILE.File=${log4j.logpath}/logfile.log
Log4J replaces ${log4j.logpath} with the system property log4j.logpath
(at least thats what happens in log4j 1.2.15 when using configuration
You will have to read the documentation and see how stuff is loaded and
whether or not it is possible. I remember seeing a page that specifically
listed the order in which LOG4J tries to search for configuration files. So
you MIGHT be able to do this. Allow LOG4J to load the configuration file
On Wednesday 06 May 2009 03:04:59 pm Marc Farrow's cat walking on the keyboard
wrote:
> I am not sure what the problem is, because the example I posted was totally
> in the program and not in a properties file.
Sorry, allow me to explain it better. I've got an application with its log4j
configur
I am not sure what the problem is, because the example I posted was totally
in the program and not in a properties file.
Luca Ferrari wrote:
>
> On Tuesday 05 May 2009 08:15:38 pm Marc Farrow's cat walking on the
> keyboard
> wrote:
>> I am fairly new to LOG4J, but you can set up a Properties
On Tuesday 05 May 2009 08:15:38 pm Marc Farrow's cat walking on the keyboard
wrote:
> I am fairly new to LOG4J, but you can set up a Properties object in your
> application and use that to initialize the LOG4J engine. Here is a small
> snippet of code to get you started. So with this method, you
