Link Details

sorry, pointless. you can check the static version at compile time using checkstyle, etc.

I'm not sure I understand your negative vote. Log4J obviously have a serious flaw in how loggers are defined. You are probably right that you can use some third-party tool to check what you've done is correct, but that does not negate the fact that the approach I suggest for acquiring loggers are easier and will ALWAYS work. Conventions are easiest upheld when they are automatic...

Interesting idea.

Thanks.
Yes the idea of implementing a 'thisclass' as done here can be used in a number of places. I found it really useful for the Log4J stuff, hence my blog...

You can also inject the logger at runtime:

@Logger private log;

Oops, I meant:

@Logger private Logger log;

Hi behrangsa

thanks for the comment. What framework are you using for this?
Can you make the log variable static? if not you are not much better off than using the Logger.getLogger( this.getClass() )

IntelliJ code generation template worked for me, so I haven't really looked for other ways. Guice (http://code.google.com/p/google-guice) is supposed to be able to do this kind of things. Another trick I can think of:

class ... {

 final static Class me = new Whatever() {}.getClass().getEnclosingClass();

}

That's a nice one, I should probably include this in the article. Its JDK5+ only isn't it?

Yup. There is also a getDeclaringClass() http://java.sun.com/javase/6/docs/api/java/lang/Class.html#getDeclaringClass() but one time I tried it, it didn't return what I expected.

Thanks for your comments. I think its worth extending the article with annonymous subclasses and loggers.. it surely is something that you can't check with checkstyle! :-)