No, I have not, but it's low priority for me. I haven't fully explored solutions to this.
> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Serodio > Sent: Thursday, May 25, 2006 6:45 AM > To: [email protected] > Subject: Re: Rehashing question about consequences of using > configureAndWatch in a servlet > > Karr, David wrote: > > <snip> > > > I would guess the way to rectify this would be to write > your own loop > > in a thread that watches the log4j.xml file, with a timeout on each > > iteration, which checks a static flag that could be set in the > > "destroy()" method. > > > > If "configureAndWatch()" in a servlet is really unsafe, I > find it hard > > to believe someone hasn't written a reusable replacement for > > "configureAndWatch()" that can exit on command. > > David, have you found a solution for this? I was just about to use > configureAndWatch() when I saw this post. > > Thanks, > Daniel Serodio > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
