cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Logging framework
Date Tue, 18 Sep 2007 00:43:10 GMT


All creation of Logger objects now go through the 
LogUtils.createL7nLogger(...) calls.   Thus, IMO, you should just update 
those two methods to wrapper things like Log4j with something that 
implements the Logger interface and return that.   That would be the 
lowest impact on existing code, we could all still use the j.u.l API's, 
etc... (except we need to make sure to create the loggers through 
LogUtils, which we should anyway for i18n reasons.)


On Monday 17 September 2007, Guillaume Nodet wrote:
> It seems CXF logging uses java.util.logging, which is fine
> for a standalone product, but not so fine when integrating CXF
> inside another product (thinking about geronimo, servicemix, etc...).
> The main problem is that lots of products uses log4j or another
> logging mechanism, and not being able to integrate and use the
> same logging mechanism is imho a real pain for users who want to
> debug and see what happens.
> I'm thinking about creating a interface
> org.apache.cxf.common.logging.Logger that would be used instead of the
> java.util.logging.Logger class.  The LogUtils
> helper class would reuse a default implementation using
> java.util.logging, while other products could implement their own
> version to wrap their preferred logging api.
> Thoughts ?

J. Daniel Kulp
Principal Engineer
P: 781-902-8727    C: 508-380-7194

View raw message