Jason, This is something that I'm currently working on as well. This is not just for Log4J but for a whole series of "components" in a J2EE application which "logging" is just one piece. Basically, I defined a Java interface for "Refresh" that defines a "refresh()" method. All classes that want to can implement this interface and define their own "refresh()" method. Now I have a web page that displays the current settings including logging and changing these values and doing a system-wide "refresh" causes each of those classes within my packages to have their "refresh()" method called.
Is something like what you're thinking about? _________________________ Rob Mitchell Base Class Technologies, Inc. Java, WebSphere, Domino, Oracle development [EMAIL PROTECTED] ----- Original Message ----- From: "Jason Poley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 03, 2002 9:02 PM Subject: Memory based config > I have a question regarding the log4j properties file. Is there any > current way (or plans to) have a means of storing the config settings in > memory and editing them on the fly (instead of having to edit the > properties file and wait for a reload?) > > This is functionality that I would like to use, and was wondering if there > was anyone else who would need/want this. > > -jason > > > -- > 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]>
