Quoting Max Rydahl Andersen <[EMAIL PROTECTED]>: > Hi guys, > > I like the UGLI approach - simple and efficient. >
You do realize that UGLI has been dropped in favor or SLF4J, right? http://slf4j.org/ It's really the same concept with a different name, and under a license that is compatible with both Apache and GPL/LGPL licenses. There has also been further development as well. I suggest you check that out as the next non-1.2.x version of Log4j will work with slf4j, not UGLI. > But one thing bothers me - why don't you have Logger.log(lvl, msg, ...) in > there to > support custom levels which all the ugli implementors support ? > I suggest you sign up on the slf4j email list and make your suggestion there. The Log4j project does not steer development of slf4j (although some slf4j developers may happen to Log4j developers... as well as commons-logging developers). As to the response by Alexey where he said... > Btw, there is no need to introduce another API - the same efficient > solution with a direct implementation of another interface can be done > for commons-logging API also. This may be the case (I'll have to trust you on this one), but it isn't a common usage pattern of commons-logging. The normal usage pattern is for commons-logging to be a wrapper and use discovery to find the logging implementation. As Ceki has shown ( http://www.qos.ch/logging/classloader.jsp ), this discovery mechanism is only reliable when the logging implementation is "located at the same level or higher in the class loader tree", so "in practical terms, the only logging API safely bridged by JCL is the java.util.logging API". Ceki's article contrasts UGLI with commons-logging. Of course, as I've said, UGLI has been replaced by slf4j, so you can just replace any mention of UGLI with slf4j. Jake > /max > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
