The reason given at the presentation at JavaOne was primarily that you can't
have static methods in interfaces. IMO, for example, it sure would be nice
if the Category and Priority classes in Log4j was an interface instead of
classes -- it sure would be easier to extend them. Unfortunately, there are
practical "issues" with doing that, and Sun faces the same issues.
-Jim Moore
-----Original Message-----
From: Kent Yang [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 31, 2001 9:16 PM
To: LOG4J Users Mailing List
Subject: Re: JSR47 vs. log4j (take two)
I am encourage by the latest developments. However, I wonder why
Sun didn't just specify an interface and allow different logging backends
to be plug-in. That way developers can decide what implementation
they want to use. Sun did this with a lot of their APIs (Security, Sockets,
etc...) Can this be done? Is there some reason log4j can't be the engine
behind a specified interface? I am still a newbie with the log4j API (I
know
you can plug in different appenders) but I am no log4j expert and I
don't know enough about the innerds to know whether this is possible
or not.
Mabye someone else can comment?
Kent
----- Original Message -----
From: "Ceki Gülcü" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 5:18 PM
Subject: JSR47 vs. log4j (take two)
For the latest developments on the JSR47 front you might want to read:
http://jakarta.apache.org/log4j/docs/critique2.html
--
Ceki Gülcü - http://qos.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
