This is a possibility. I don't know if people want to avoid a third party library dependency... Jetty for example has its own Logger interface that can be easily implemented. See http://svn.jetty.codehaus.org/browse/jetty/jetty/trunk/modules/util/src/main/java/org/mortbay/log
On 9/18/07, James Mao <[EMAIL PROTECTED]> wrote: > > Something like this http://www.slf4j.org/? > > James > > > 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 ? > > > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
