Apache Commons EqualsBuilder and HashCodeBuilder

2019独角兽企业重金招聘Python工程师标准>>>

Introduction

Before we go ahead and explore Apache Commons**_ EqualsBuilder_** and HashCodeBuilder, we must know the relationship between equals and hashCode.

java.lang.Object which is the super class of all Java classes has two very important methods defined in it. They are:

public boolean equals(Object obj)

public int hashCode()

These two methods are very important when our classes deal with other Java classes such as Collection API used for searching, sorting, comparison and eliminate duplicate objects from a set.

public boolean equals(Object obj)

This method checks if some other object passed to it as an argument is equal to the object on which this method is invoked. The default implementation of this method in ** Object** class simply checks if two object references x and y refer to the same object, i.e., it checks if ** x == y**. This particular comparison is also known as “shallow comparison”. However, the classes providing their own implementations of the equals method are supposed to perform a “deep comparison”

public int hashCode()

This method returns the hash code value for the object on which this method is invoked. This method returns the hash code value as an integer and is supported for the benefit of hashing based collection classes such as Hashtable, HashMap,_ HashSet_, etc.

Relationship between equals and hashCode

Equal objects must produce the same hash code as long as they are equal, however unequal objects need not produce distinct hash codes.

Implementation

While_** hashCode()_ and_ equals()_ typically impact logic and performance, they are also often more tricky to implement correctly. The most important rule is that when one of these two methods is overridden, the other one should be as well. Because it can be tricky to implement hashCode() and equals() correctly, it is helpful to have_ EqualsBuilder_** and_** HashCodeBuilder**_ two reusable implementations of these provided as part of Apache Commons Lang builder package.

I particularly like the way how EqualsBuilder uses reflection to determine if the two Objects are equal or HashCodeBuilder uses reflection to build a valid hash code. But reflection hits the performance of application, so use it where the performance is not very critical. However these two builders also provide the alternative approach. Let’s demonstrate both approaches one by one:

• Using Reflection:

Let’s create a simple class called Employee as the following mentioned code:

package blog.commons;

import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;

public class Employee {

	private int id;
	private String name;
	private int deptId;
	private String designation;

	public Employee(int id, String name, int deptId, String designation) {
		this.id = id;
		this.name = name;
		this.deptId = deptId;
		this.designation = designation;
	}

	@Override
	public boolean equals(Object obj) {
		return EqualsBuilder.reflectionEquals(this, obj);
	}

	@Override
	public int hashCode() {
		return HashCodeBuilder.reflectionHashCode(this);
	}
}

Now create a _ Main_ class to check how it works:

package blog.commons;

import java.util.Arrays;
import java.util.HashSet;
import java.util.Set;

public class Main {

	public static void main(String[] args) {
		Employee emp1 = new Employee(1, "Allen", 12, "Accountant");
		Employee emp2 = new Employee(1, "Allen", 13, "Accountant");
		System.out.println
			("Is emp1 equals to emp2: " + emp1.equals(emp2));
		Set<Employee> employees = new HashSet<Employee>();
		employees.addAll(Arrays.asList(emp1,emp2));

		System.out.println("Size of set: " + employees.size());

	}
}

If you execute the**_ main_** method, the output will be as follows:

Is emp1 equals to emp2: false
Size of set: 2

Here you can see that the employee “Allen” whose employee Id is “1? is an “Accountant” does his book keeping job for two different departments which department ids are**_ 12_** and 13 respectively. But the object**_ emp1_** and emp2 are treated as two different persons.

Now, let’s exclude the**_ deptId_** field to determine equality and build hashCode and see the effect. For doing this, you need to slightly modify the code of Employee class:

package blog.commons;

import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;

public class Employee {

	private int id;
	private String name;
	private int deptId;
	private String designation;

	public Employee(int id, String name, int deptId, String designation) {
		this.id = id;
		this.name = name;
		this.deptId = deptId;
		this.designation = designation;
	}

	@Override
	public boolean equals(Object obj) {
		return EqualsBuilder.reflectionEquals
			(this, obj,new String[] {"deptId"});
	}

	@Override
	public int hashCode() {
		return HashCodeBuilder.reflectionHashCode
				(this,new String[] {"deptId"});
	}
}

Again, execute the same**_ main_** method to see the output:

Is emp1 equals to emp2: true
Size of set: 1

Here, as you can see, now**_ emp1_** and emp2 are treated as equal but**_ emp1_** are been replaced by emp2, hence the size of the set employees is one. To overcome this problem, do not exclude the deptId while generating hashCode. Your**_ hashCode_** method should look like the following:

@Override
	public int hashCode() {
		return HashCodeBuilder.reflectionHashCode(this);
	}

Now the output should be shown as below if you execute the**_ main_** method again:

Is emp1 equals to emp2: true
Size of set: 2

• Without Using Reflection:

In my previous examples, you have seen how easily and in a fascinating manner we can use reflection capability of EqualsBuilder and HashCodeBuilder to override**_ equals _**and hashCode methods. Now, I am going to show you how can you achieve the same output without using reflection which helps to improve performance:

package blog.commons;

import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;

public class Employee {

	private int id;
	private String name;
	private int deptId;
	private String designation;

	public Employee(int id, String name, int deptId, String designation) {
		this.id = id;
		this.name = name;
		this.deptId = deptId;
		this.designation = designation;
	}

	@Override
	public boolean equals(Object obj) {
		if (obj instanceof Employee == false) {
			return false;
		}

		if (this == obj) {
			return true;
		}
		Employee other = (Employee) obj;
		return new EqualsBuilder().append(this.id , other.id)
		.append(this.name , other.name)
		.append(this.designation , other.designation).isEquals();
	}

	@Override
	public int hashCode() {
		return new HashCodeBuilder().append(this.id)
		.append(this.name)
		.append(this.deptId)
		.append(this.designation)
		.hashCode();
	}
}

If you run the _ main_ method this time, you get similar output as it has been shown in the last output result. Just notice here that I am not appending deptId in _ EqualsBuilder_ but I am doing it while generating _ hashCode_.

转载于:https://my.oschina.net/u/3238650/blog/1248260