Yeah, I know, there is no class.this in the static context. And I also duplicate the classname. I have not found it a problem though, in the sense of copy-paste bugs. But it can happen, I agree. I *would* like the simple non-parameter, getLogger()-call, if I can be sure, the “one-up in the call stack” implementation always hold. That was a question!?

For printf: For me, I don’t care much for “log.isDebugEnabled” anymore. I used to, though. For me, printf over string concat is all about better readability of the code, now. Sure, there can be specific places where isDebugEnabled() makes sense (like an expensive loop, debugging something out), but they are rare. In my opinion. I really like having readable code, an area where printf shines more than string concat, I think.

Which is reasonable. The point is that there is no “class.this” reference to the enclosing class in java, and copy-paste problems could occur, apart from the typing of redundant information.

As for the printf, I don’t know who would want to use something as slow in a logging statement. Is this a feature to have nicer printing lines or to remove the need to do this?
[code]
if (log.isInfoEnabled(…)) {
…
}
[code]