Absolutely. One of the advantages of the "login" approach is that it avoids this problem, since only users who are able to login can trigger the reload.
--- regards --- Larry
At 01:45 PM 11/11/03, you wrote:
BTW, reloading via a servlet in this way has some potential security implications, so tread carefully.
Ken
> -----Original Message----- > From: Liu, Ken (C) > Sent: Tuesday, November 11, 2003 3:41 PM > To: [EMAIL PROTECTED] > Subject: RE: automatic reload > > > > I don't know, perhaps my solution is too simplistic or too > > low-tech, but for a webapp, I simply have a URL that I ping > > when I change > > the log4j config file. Since the config file doesn't change > > automatically, > > This is the approach I use. I have a servlet that calls > configure(). I > also have it set up to accept a url parameter, in case I want > to reload a > log4j config file from a url (we developers don't always have > access to the > file system).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------
Larry Young
The Dalmatian Group
www.dalmatian.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
