Scott,
That would be great, and indeed, an argument would do the job as well.
dirk
> -Original Message-
> From: Scott Deboy [mailto:[EMAIL PROTECTED]
> Sent: vrijdag 25 februari 2005 19:18
> To: Log4J Users List
> Subject: RE: Specify chainsaw config file in webStart li
Original Message-
From: OOMS DIRK [mailto:[EMAIL PROTECTED]
Sent: Fri 2/25/2005 6:30 AM
To: 'Log4J Users List'
Cc:
Subject: RE: Specify chainsaw config file in webStart link
After having looked more into it, i believe i need to clarify my earlier
question. I wo
ruari 2005 18:43
> To: 'Log4J Users List'
> Subject: RE: Specify chainsaw config file in webStart link
>
>
> Scott,
>
> I tried out your below suggestion: adding name="log4j.configuration"
> value="http://myServer/myLog4jConfig.xml"; />t
"must". In the former case I could try to trace down whether
something goes wrong in the chainsaw code.
Cheers,
dirk
> -Original Message-
> From: Scott Deboy [mailto:[EMAIL PROTECTED]
> Sent: vrijdag 21 januari 2005 17:30
> To: Log4J Users List
> Subject:
2005 7:58 AM
To: 'log4j-user@logging.apache.org'
Cc:
Subject: Specify chainsaw config file in webStart link
Hello,
I am thinking of building a web application that allows the user to
configure a subset of the log4j configuration parameters in a 'user
friendly' way (
Hello,
I am thinking of building a web application that allows the user to
configure a subset of the log4j configuration parameters in a 'user
friendly' way (so he/she does not have to know all log4j configuration
details). At the same time I will generate the corresponding chainsaw config
file on
