On Apr 6, 2006, at 12:36 AM, Mark Womack wrote:
I checked in a bunch of changes. Hopefully it isn't more broken
than before. The tests for FileWatchdog are just too intricate.
The config file could be getting read by watchdog, so can't be
deleted as required in the tests, so I had to add some code to loop
on deleting. Then it seems that it can take some time for the
appender buffer to flush to the file, etc. Most of this intricacy
is because of the nature of the test. In real world usage I don't
think it would be this complex.
We'll see if Gump complains tonight.
-Mark
Also, I'm not sure how the FileWatchdog stuff would interact with
restoring DOMConfigurator for log4j 1.2 compatibility (http://
issues.apache.org/bugzilla/show_bug.cgi?id=39024).
configureAndWatch has some very peculiar behavior and I don't think
it will carry over into log4j 2.0. So perhaps, restoring the 1.2
DOMConfigurator and omitting configureAndWatch from JoranConfigurator
would make all the FileWatchdog stuff moot.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
