How to decouple logging implementation and API?

I'm creating a small Java framework, which will log its events. I don't want the framework to be dependent on any particular logging implementation (jul, commons logging, log4j, slf4j, logback, etc). Instead, I want to allow my clients to choose anything they prefer.

The question开发者_如何学编程 is - how should I realize such decoupling? How my framework should log its events?

---

slf4j is designed to solve exactly this problem: it decouples the API from the logging implementation.

slf4j is not a logging implementation by itself. It depends on the existence of a back-end implementation. Logback just happens to natively implement the slf4j API but there are bindings for log4j, java.util.Logging and others.

At some level you must have an API for your clients to use. You might as well make it one of the existing APIs rather than writing your own.

---

I think that will be difficult to achieve as your code must call something in order to log information and error messages. I think you will have to choose one (I recommend slf4j) and stick to it - this seems to be what is generally done by everyone else.

---

I would include support for AspectJ and Commons Logging.