We have developped an application that can run stand alone as well as in
applet mode. It uses log4j default initialisation (log4j.properties in
classpath) to initialize the logging system
In stand alone mode, all works fine.
The problem occurs when using it as an applet. The first time the applet
loads the logger initializes as espected. If for some reason the applet
gets reloaded (the user presses the reload button) , the automatic
initialisation is performed again (automatically by log4j). The problem
is that the 'old' appenders from the first initialisation continue to
exist. This means that every logging statement will be logged twice
now. After another reload, all statements will be logged three time
etc.. The only solution to stop this excessive logging is to restart the
browser.
I wonder if there exist some trick to force the default initialisation
procedure to do a cleanup of old appenders before adding the new ones
specified in log4j.properties.
If you know one , please let me know,
Koen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
