Skip to main content

Why we must declare immutable class as Final? Why is an immutable class supposed to be final?

Why immutable class declared as final in Java?

Why we must declare immutable class as Final

Immutable class means, once object is created it can not be changed. 

Learn more about Immutable class in details :

Now lets see why we must declare immutable class as final in Java.

If immutable class does not defined as final then any other class can extends that class and change properties of that class and broke the objective of immutability.

So final class is important in immutability. Lets see using example.

Programming.java

public class Programming {
    
    private final String name;
    
    public Programming(String name) {
        this.name = name;
    }

    public String getName() {
        return name;
    }

    @Override
    public String toString() {
        return "Programming [name=" + name + "]";
    }

    @Override
    public int hashCode() {
        final int prime = 31;
        int result = 1;
        result = prime * result + ((name == null) ? 0 : name.hashCode());
        return result;
    }

    @Override
    public boolean equals(Object obj) {
        if (this == obj)
            return true;
        if (obj == null)
            return false;
        if (getClass() != obj.getClass())
            return false;
        Programming other = (Programming) obj;
        if (name == null) {
            if (other.name != null)
                return false;
        } else if (!name.equals(other.name))
            return false;
        return true;
    }

}

MutableClass.java

public class MutableClass extends Programming {

    private String mutableName;
    
    public MutableClass(String name) {
        super(name);
       
        // Setting same name as programming name field
        this.setMutableName(name);
    }

    public String getMutableName() {
        return mutableName;
    }

    public void setMutableName(String mutableName) {
        this.mutableName = mutableName;
    }

    @Override
    public int hashCode() {
        final int prime = 31;
        int result = super.hashCode();
        result = prime * result + ((mutableName == null) ? 0 : mutableName.hashCode());
        return result;
    }

    @Override
    public boolean equals(Object obj) {
        if (this == obj)
            return true;
        if (!super.equals(obj))
            return false;
        if (getClass() != obj.getClass())
            return false;
        MutableClass other = (MutableClass) obj;
        if (mutableName == null) {
            if (other.mutableName != null)
                return false;
        } else if (!mutableName.equals(other.mutableName))
            return false;
        return true;
    }
    
}

Demo.java

import java.util.HashMap;

public class Demo {

    public static void main(String[] args) {
       
        HashMap<Programming, Integer> mapOfProgramming = new HashMap<>();
       
        MutableClass mutableObj = new MutableClass("Java");
       
        // Assigning obj reference of mutable to immutable class
        Programming programmingObj = mutableObj;
       
        mapOfProgramming.put(programmingObj, 1);
       
        // Changing immutable class property "name" using mutable class
        mutableObj.setMutableName("Python");
       
        System.out.println(mapOfProgramming.get(programmingObj));
       
    }
    
}

Output :

null

As you can see, we are getting "null" answer rather than "1". because MutableClass extends Programming class and change the property of "name" field and broke the immutability of Programming class.

Map only knows key holding as Object "Java", but using mutable class we are set name property to "Python" and if we get from map using "Python" name property it will return null because there is no key as name "Python". 

If we comment "mutableObj.setMutableName("Python");" line of code we are getting answer as 1.

So for create immutable class, one must declare class as Final otherwise some other class can extends it and change the object of immutable class.


Other articles :

 

Comments

Popular posts from this blog

Flipping the Matrix HackerRank Solution in Java with Explanation

Java Solution for Flipping the Matrix | Find Highest Sum of Upper-Left Quadrant of Matrix Problem Description : Sean invented a game involving a 2n * 2n matrix where each cell of the matrix contains an integer. He can reverse any of its rows or columns any number of times. The goal of the game is to maximize the sum of the elements in the n *n submatrix located in the upper-left quadrant of the matrix. Given the initial configurations for q matrices, help Sean reverse the rows and columns of each matrix in the best possible way so that the sum of the elements in the matrix's upper-left quadrant is maximal.  Input : matrix = [[1, 2], [3, 4]] Output : 4 Input : matrix = [[112, 42, 83, 119], [56, 125, 56, 49], [15, 78, 101, 43], [62, 98, 114, 108]] Output : 119 + 114 + 56 + 125 = 414 Full Problem Description : Flipping the Matrix Problem Description   Here we can find solution using following pattern, So simply we have to find Max of same number of box like (1,1,1,1). And ...

How to Implement One to Many and Many to One Mapping in Spring Boot using JPA

Spring Boot CRUD example using One-to-Many and Many to One mapping | With Thymeleaf User Interface In this tutorial, we will learn how to use @OneToMany and @ManyToOne annotation using JPA (Java Persistent API) in Spring Boot. We also attach Thymeleaf for User Interface. In past tutorial, we already created Spring Boot CRUD with Rest API, JPA and MySql. Please refer that one first, we will continue from there. Spring Boot application with Thymeleaf, Rest API, JPA and MySql Database    For applying One to Many relationship, we need another POJO class. In past we already created Book class, now we will create new class Author . As we know Author have multiple Books, so we can easily apply One to Many operation. Lets create POJO class for Author and apply @OneToMany on Book .  Define List of Book and apply @OneToMany annotation on field. We are using mappedBy property, so Author table does not create new column.  We already learn about mappedBy property in One-to-One a...