You can look at the code, but in the current version, there is no mechanism to stop a Watchdog after it is created and started. In fact, each time you call configureAndWatch(), it creates a new instance of a Watchdog. So, you can potentially have multiple Watchdogs watching the same file and stepping over each other. Unless I am missed something in the code.
I am working on a some proposed code that will enhance the Watchdog implementation so that you can have better control over this. The new design also does not require a configureAndWatch() method in the configurator class; it will potentially work with any configurator. There are also more Watchdog types, like one that watches an http url on a web server. I submitted an initial version to the dev list, and I am working on updating it to incorporate the first round of feedback. If you are interested in looking at it, contact me directly. I would appreciate the feedback. -Mark -----Original Message----- From: Charlie Cano [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 10:13 AM To: [EMAIL PROTECTED] Subject: Turning of conf file watching Hey all, Quick question: If I initialize a PropertyConfigurator with PropertyConfigurator.configureAndWatch("myConfFile", 1000); is there anyway I can turn that watch off? The API doc is not clear on this issue. I basically want the ability to, at some future point, programmatically stop checking the configuration file and auto-loading the configuration. Is this possible? Thanks in advance, Charlie -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
