On Fri, 4 Mar 2005 14:28:54 -0500, Rahul P Akolkar <[EMAIL PROTECTED]> wrote:
> Martin,
> 
> Thanks for your input. I'm not trying to re-invent anything, the last
> thing we need is a new "logging abstraction" ;-)
> 
> > As I understand it, the only dependency is Commons Logging.
> > Log4j is optional - you only need it if that's the particular
> > logging implementation you want to use.
> 
> Are you sure? I dropped taglibs-log.jar in WEB-INF/lib and visited this
> JSP:
> 
> <%@ taglib prefix="log" uri="http://jakarta.apache.org/taglibs/log-1.0"%>
> <log:info>Lets hope we don't have any other dependency!</log:info>
> 
> to be greeted with:
> 
> java.lang.NoClassDefFoundError: org/apache/log4j/Priority
> 
> Not sure where the log4j default assumption came from.

Been a while, but I'm pretty sure that the released log taglib (1.0)
uses log4j, while the current CVS HEAD was changed to use whatever
version of commons-logging was available at the time.

(I didn't write the taglib, but I did do the release and the change to
clogging).


> 2) If the above log4j dependency is true, then the usage of the log taglib
> within the rdc taglib has already bound the rdc-based app developer to
> log4j (for the one log argument). Personal preference is one thing, I
> definitely would not want to insist on a log4j dependency for all RDC
> based apps.

Shouldn't be that hard to release a 2.0 of the log taglib. Or 1.0 of a
commons-logging taglib (rename the existing one), and maybe a 1.0 of a
UGLI taglib.

> > On every project I have worked on that uses JDK 1.4 as a minimum,
> > we have used Log4j over JDK logging.
> 
> Over JDK logging? I'm interested in knowing what taglib you used for your
> JSP logging.
> 
> > As Ceki (Mr. Log4j) and others have said many times, JDK 1.4
> > logging is like they based it on Log4j concepts but left out the good
> > parts. ;-)
> <snip>
> > Anything that works with Commons Logging works with JDK 1.4 logging
> > already.
> 
> Well, am sure some of our friends are working on that ;-) I am not
> interested in debating which one is better, I've gone through reviews and
> now-famous blog postings ;-) But I do want the choice as a taglib author!
> I do not see the JDK option being available at all, and if that is indeed
> the case, maybe its time to change that.

logging.apache.org do have their UGLI (or something..JULI?) interface
which is a competitor to clogging now.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to