Log4j has configureAndWatch which looks for changes to the configuration file. As for commons-logging it doesn't have it yet:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg10152.html
So the other suggestion of having an action to reload or change the level is probably your best bet right now.
Woodchuck wrote:
hi Shinobu,
thanks for your reply. sorry, but i meant arbitrarily (at any time),
rather than hard-coding logic in the code to toggle the debug flag at
certain known situations.
what i thought was, if possible, it would be nice if we could somehow get the debug flag to read (poll) from some configuration file or something, so that we can change this configuration file to enable/disable logging (or even level of logging) in the application (esp. running in production). i can see this being useful to minimize logging activity in production until there is a problem, then turn on logging to investigate and turn off when fixed, etc.
does commons-logging allow for something like this?
woodchuck
--- Shinobu Kawai <[EMAIL PROTECTED]> wrote:
Hi Woodchuck,
how can we toggle the debug flag during runtime? is it possible?or
does it require restarting the application?
Depends on how you implement it, I guess. I use commons-logging, which completely depends on the underlying logging framework; log4j by default. With log4j, you can Logger#setLevel() to change logging level at runtime. Never wanted to, though...
Best regards, -- Shinobu Kawai
-- Shinobu Kawai <[EMAIL PROTECTED], [EMAIL PROTECTED]>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jason Lea
