What is the use of interface constants?

by

Putting static members into an interface (and implementing that interface) is a bad practice and there is even a name for it, the Constant Interface Antipattern, see Effective Java, Item 17:

The constant interface pattern is a poor use of interfaces. That a class uses some constants internally is an implementation detail. Implementing a constant interface causes this implementation detail to leak into the class’s exported API. It is of no consequence to the users of a class that the class implements a constant interface. In fact, it may even confuse them. Worse, it represents a commitment: if in a future release the class is modified so that it no longer needs to use the constants, it still must implement the interface to ensure binary compatibility. If a nonfinal class implements a constant interface, all of its subclasses will have their namespaces polluted by the constants in the interface.

There are several constant interfaces in the java platform libraries, such as java.io.ObjectStreamConstants. These interfaces should be regarded as anomalies and
should not be emulated.

To avoid some pitfalls of the constant interface (because you can’t prevent people from implementing it), a proper class with a private constructor should be preferred (example borrowed from Wikipedia):

public final class Constants {

    private Constants() {
        // restrict instantiation
    }

    public static final double PI = 3.14159;
    public static final double PLANCK_CONSTANT = 6.62606896e-34;
}

And to access the constants without having to fully qualify them (i.e. without having to prefix them with the class name), use a static import (since Java 5):

import static Constants.PLANCK_CONSTANT;
import static Constants.PI;

public class Calculations {

    public double getReducedPlanckConstant() {
        return PLANCK_CONSTANT / (2 * PI);
    }
}

More Related Contents:

  1. What is the point of abstract classes, when you could just do an interface [duplicate]
  2. How can I get a list of all the implementations of an interface programmatically in Java?
  3. Is there more to an interface than having the correct methods
  4. Implements vs extends: When to use? What’s the difference?
  5. Why does the behavior of the Integer constant pool change at 127?
  6. Abstract class vs Interface in Java
  7. Do interfaces inherit from Object class in java
  8. Protected in Interfaces
  9. Purpose of Default or Defender methods in Java 8
  10. Should we @Override an interface’s method implementation?
  11. When should I use an interface in java? [closed]
  12. Java8: Why is it forbidden to define a default method for a method from java.lang.Object
  13. What are the differences between abstract classes and interfaces in Java 8?
  14. Why do we need interfaces in Java?
  15. Do/can abstract classes replace interfaces? [duplicate]
  16. Finding SSID of a wireless network with Java
  17. Explaining Interfaces to Students [closed]
  18. In Java when one interface extends another, why would one redeclare a method in a subinterface?
  19. Why no static methods in Interfaces, but static fields and inner classes OK? [pre-Java8] [duplicate]
  20. Why is there no Constant feature in Java?
  21. What is the purpose of the default keyword in Java?
  22. Java: Interface with new keyword how is that possible?
  23. Are defaults in JDK 8 a form of multiple inheritance in Java?
  24. interface as a method parameter in Java
  25. When is an interface with a default method initialized?
  26. Java casting in interfaces
  27. Java interfaces and return types
  28. In Java why this error: ‘attribute value must be constant’?
  29. The purpose of interfaces continued
  30. How to serialize a class with an interface?

Leave a Comment