The class should not contain a nested class unless the nested class is to be a utility class as well (though this practice is potentially complex and hurts readability). Methods in the class should …

Aug 30, 2012 · A Utility class is understood to only have static methods and be stateless. You would not create an instance of such a class. A Helper can be a utility class or it can be …

Dec 6, 2016 · Similarly, utility methods can and should be placed in a class named for specific functionality, not “miscellaneous stuff related to bread.” Most of the time, your static methods …

Class should not have any non-final or non-static class fields. As you've asked, the class name cannot be abstract (not advisable) -> Which means you are planning to implement it in another …

Oct 14, 2011 · The final keyword on a Java class prohibits other classes from extending (inheriting from) it. If you don't make a class final, an extending class can make use of all sorts …

Aug 16, 2011 · If you're using a dependency injection framework (Spring, Guice, whatever), it might be a good idea to just make the utility class instantiatable, with non-static methods, and …

I consider utility classes to be a code smell, but sometimes they are required to reuse methods that do not fit in any other class. I prefer filename with Utils suffix as it includes various …

Don't use utility classes where static or instance methods in a domain class would be a better solution. For example, consider if methods in an abstract base class or an instantiable helper …

Apr 6, 2011 · You can also check out the Java language specification on Arrays. Using the Arrays Utility Class. java.util.Arrays contains a bunch of static methods. Static methods belong to the …

Sep 24, 2016 · Abstract obviosuly indicates that the class is meant to be extended - using this keyword is misleading which is why the approach used by Sun, Oracle, and Google is to not …