What is meant, exactly, by "modify log4j settings at runtime"? From a
org.apache.log4j.gui.ChangeLoggingDialog within the application being run?
Sending it a SIGHUP to reread the file? From another VM that talks over a
socket?
-Jim Moore
-----Original Message-----
From: Ceki Gulcu [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 19, 2001 3:14 AM
To: LOG4J Developers Mailing List
Subject: Re: Log4J beyond 1.1, thunderdome!
At 03:00 19.05.2001 +0200, you wrote:
>Hello,
>
>To be able to plan the next releases of log4j, we would like to know what
>new features/enhancements/changes/wishes you have in mind for log4j beyond
>1.1.
>Please voice them on the [EMAIL PROTECTED] mailing list.
Good idea.
>Also:
>- is the current documentation sufficient?
Documentation is almost never sufficient but again nobody has time to read
documentation anyway. :-)
>- a servlet to view the log (and sort, list, print), would this be usefull?
Yes, definitely.
>- a servlet to modify the log4j.properties, or is this overkill?
A facility to modify log4j settings at runtime is probably the most
important feature that is currently missing. As a corollary, the user should
be able to instruct log4j to spit out the current settings as a config file
(properties or XML).
>- should log4j support i18n? (dunno if it already correctly does)
Localization support is already there. Cheers, Ceki
ps: One other feature we need is to fully integrate one of the JDBCAppenders
in contribs/.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
