If I've to distribute a certain framework like a customized validation framework which can be used in many projects, how do I handle logging within this framework so that it uses the same logging method as the project in which it is being used? i.e I've written a logger interface with the usual debug,warn,info... methods and the implementation of this interface can implement those methods using log4j or any other logging methods. If I distribute this as a jar, how can different projects use this jar with their logging framework?
1
-
6Why do you want to reinvent the wheel? There's SLF4J for that.Buhake Sindi– Buhake Sindi2011-08-08 06:27:57 +00:00Commented Aug 8, 2011 at 6:27
Add a comment
|
2 Answers
I would strongly suggest that instead of writing yet another logging framework you recode your application to use the SLF4J logging API instead. All the work of interfacing to other logging implementations have been done, and is well known in the industry.
An added benefit is that you get {}-placeholders, which allow you to just do
log.debug("a={}, b={}", a, b);
and the a.toString() and b.toString() are only called when the string will actually be logged. This allows for a lot of log statements which will not actually be executed unless you need them to run in a debug setting.
answered Aug 8, 2011 at 6:30
Thorbjørn Ravn Andersen
75.4k35 gold badges203 silver badges359 bronze badges
1 Comment
Thorbjørn Ravn Andersen
The hard part in a logging framework is to ensure good performance when logging, and excellent performance when not.
There are some libraries that provide an abstraction layer over log4j, java.util.logging etc. They act as the 'interface' and then the person using your project can use the implementation of their choosing. Have a look at Apache Commons Logging and SLF4J.
