Re: wm.log time stamp broken?

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1737191362-1144143636=:40525
Content-Type: TEXT/PLAIN; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

On Tue, 4 Apr 2006, Endre St=F8lsvik wrote:

| On Mon, 3 Apr 2006, Keats Kirsch wrote:
|=20
| | Endre St=F8lsvik wrote:
| |=20
| | > I personally use log4j for our server, so log4j would in theory sui=
t me
| | > totally nice, but considering that there are both log4j and the now=
 rather
| | > prevalent jsr 47 (java.util.logging) and some other fringe stuff, i=
t seems
| | > slightly backwards to go with one specific system.
| | >=20
| | > Regards,
| | > Endre
| | > =20
| | I agree.  I think we should look at the JCL
| | (http://jakarta.apache.org/commons/logging/) since it already provide=
s
| | adapters for java.logging and Log4J, etc.
|=20
| And again, SLF4J.
|   http://www.slf4j.org/
|=20
| This uses a very different "resolving" than clogging (=3D=3Djcl), in th=
at you=20
| actually include a specific implementation of the "logging facade": you=
=20
| simply add one of several jars to the classpath, e.g. a slf4j-log4j.jar=
,=20
| or slf4j-jsr47.jar, or a simple slf4j-stderr.jar. (Names have been fake=
d,=20
| to protect me from actually having to look them up)=20
|   Ceki G=FClc=FC (the founder of log4j) started this as a reaction to l=
ots of=20
| problems with the clogging-paradigm, that has to do with classloaders i=
n=20
| multi-cl systems, _typically_ servlet containers, tomcat. Since slfj4 u=
ses=20
| a _static_ linking, such problems are thus avoided.

Reading this message, I find that I sound like an evangelist. I'm not.

I just wanted to point out that there are _two_ solutions to the=20
underlying problem. The oldest is commons logging / jcl / "clogging". Thi=
s=20
doesn't come without problems, in particular in servlet container=20
scenarios, and to address these problems, slf4j has been developed. These=
=20
are "very competing" in how they solve the problem at hand.

I'm not sure which one is best - I don't think there is a clear-cut=20
answer, and the answer will probably be different for different settings.=
=20
One should be sure that one actually _understand_ the two solutions and=20
their problems before blasting out with "obviously slf4j is best, always!=
"=20
or the opposite.
  But I do think that both solutions must be known by the community befor=
e=20
a decision is made!

Regards,
Endre.
--0-1737191362-1144143636=:40525--


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642