Is it bad practice for a class to have only static fields and methods?

Question

I have a class that consists only of static member variables and static methods. Essentially, it is serving as a general-purpose utility class.

Is i

Answer 1

This link http://java.dzone.com/articles/why-static-bad-and-how-avoid seems to go against most of the answers here. Even if it contains no member variables (i.e. no state), a static class can still be a bad idea because it cannot be mocked or extended (subclassed), so it is defeating some of the principles of OO