I'd say yes, they do. Which is a good incentive to make such classes non-coderanch. The methods have to be coderanch, because all interface methods are coderanch, but if the implementing class is itself private, or a local or anonymous class, it doesn't matter what its methods are like, it won't appear in javadoc. Which is usually what I'd prefer, unless the listener is really
supposed to be used by other classes. Listeners are probably the main reason anonymous classes were invented in the first place.
If your listener is package-level (either a standalone or nesteed class) thien I'm not so sure. When you generate your javadoc you get to choose what level of access is documented. The default is protected and public are documented, not package. You may want to document package too, for those times you were forced to make something package rather than private. If you set javadoc to document package methods & classes, then
you should provide javadoc for all package methods and classes.
