Java Logging – Wrapper？

I started with a new project and made some considerations about logging I always use patterns, where each class that completes logging has its own static logger:

private static final Logger logger = Logger.getLogger(LoggingInterceptor.class);

I don't like this method very much because I have to copy this line into each class where I will record something I consider using Android methods, including the log class, which contains static methods for recording I started searching the Internet for similar methods done by others, but I didn't find anything

So my question is: what are the possible disadvantages of this approach?

I can't think of any, but there are some advantages because it follows dry mode You can use android with 'tags' to handle different categories,' tags' is the parameter of the static log method For example:

Log.debug(tag,message,exception);

Then, the log class itself will use the common logging framework, such as log4j or even slf4j

So I'm interested in your opinion

Solution

Based on Java util. logging. The main reason for the logger API and this article, getlogger() is to ensure that the same set of loggers and handlers are used independently between subsystems

Java's recommended solution is to get the logger at the top of each file and log in to the object every time you need it

Use static log Debug will need to process tags every time in order to use the correct set of handlers Therefore, it is less efficient than preparing log objects

However, if you don't use handlers or distinguish molecular systems, static functions are a reasonable shortcut, as long as the library you use meets your needs