My suggestion would be to use Simple Logging Facade for Java (SLF4J) instead of your own wrapper. From its website:
The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time.
This is a moderner and preferred1 alternative to Jakarta Commons Logging (JCL). I recommend to read this article for a detailed analysis but the short version is that SLF4J doesn't suffer from the class loader problems or memory leaks observed with JCL. The author of Commons Logging himself admits it.
In case you wonder, SLF4J has been written by Ceki Gülcü which is the author of Log4J (and now works on Logback, the successor of Log4J). So this guy know a thing or two about logging and there are some chances "his" wrapper is better than mine.
In other words, there is IMHO just no point at creating a wrapper in 2010 when a nice and good one already exists.
1 Please, don't use Spring as counter example, Spring is a bad counter example (see SPR-5327).