final simply makes the object reference unchangeable. The object it points to is not immutable by doing this. INSTANCE can never refer to another object, but the object it refers to may change state.
More Related Contents:
- Change private static final field using Java reflection
- Difference between final and effectively final
- How does the “final” keyword in Java work? (I can still modify an object.)
- What is the point of “final class” in Java?
- Does use of final keyword in Java improve the performance?
- Comparing strings with == which are declared final in Java
- Why should I use the keyword “final” on a method parameter in Java?
- Why would one mark local variables and method parameters as “final” in Java? [closed]
- Lambdas: local variables need final, instance variables don’t
- Why is the String class declared final in Java?
- Why would one declare an immutable class final in Java?
- Good reasons to prohibit inheritance in Java?
- Compile-time constants and variables
- Why does the Java compiler not understand this variable is always initialized?
- final keyword in method parameters [duplicate]
- in what order are static blocks and static variables in a class executed? [duplicate]
- Must all properties of an immutable object be final?
- Why are all fields in an interface implicitly static and final?
- Final variable manipulation in Java
- Will Java Final variables have default values?
- creating final variables inside a loop
- The final local variable cannot be assigned
- Anonymous-Inner classes showing incorrect modifier
- Final arguments in interface methods – what’s the point?
- What does a variable being “effectively final” mean? [duplicate]
- Why declare a function argument to be final?
- Make private methods final?
- Initialize final variable before constructor in Java
- Java : in what order are static final fields initialized?
- Cannot reference “X” before supertype constructor has been called, where x is a final variable