Thanks for the replies. I'm not understanding Ceki's suggestion so I wrote
the attached applet to illustrate my misunderstanding.
here's the code:
public class AppletLogTest extends javax.swing.JApplet {
public void init() {
Logger root = Logger.getRootLogger();
root.setLeve
-user@logging.apache.org
Subject: Re: reusability and applet dilemma
Jeff,
Have you considered using the basic techniques already offered by the log4j
framework? For instance, you could configure log4j differently when running
as an applet.
In the init() method of your appplet, you could write
Jeff,
Have you considered using the basic techniques already offered by the log4j
framework? For instance, you could configure log4j differently when running
as an applet.
In the init() method of your appplet, you could write:
Logger timestampLogger = Logger.getLogger("TimeStamp");
time
A couple of alternatives spring to mind.
1. If you're able and prepared to use a signed applet, the security
issues may go away.
2. You could handle Logger initialisation in a static block, catch
exceptions and provide a dummy implementation of Logger so that the
remainder of your code doesn't th
