Java — SerialVersionUID in Java | Code Factory

Donate : Link

WordPress Blog : Link

Applications… : Link

Prerequisite : Serialization and Deserialization

Why so we use SerialVersionUID : SerialVersionUID is used to ensure that during deserialization the same class (that was used during serialize process) is loaded.

Example : Suppose a person who is in UK and another person who is in India, both are going to perform serialization and deserialization respectively. In this case to authenticate that the receiver who is in India is the authenticated person, JVM creates an Unique ID which is known as SerialVersionUID.

In most of the cases, serialization and deserialization both activities are done by a single person with the same system and same location. But in serialization, sender and receiver are not the same person i.e. the persons may be different, machine or system may be different and location must be different then SerialVersionUID comes in the picture. In serialization, both sender and receiver should have .class file at the time of beginning only i.e. the person who is going to do serialization and the person who is ready for deserialization should contain same .class file at the beginning time only.

Serialization : At the time of serialization, with every object sender side JVM will save a Unique Identifier. JVM is responsible to generate that unique ID based on the corresponding .class file which is present in the sender system.

Deserialization: At the time of deserialization, receiver side JVM will compare the unique ID associated with the Object with local class Unique ID i.e. JVM will also create a Unique ID based on the corresponding .class file which is present in the receiver system. If both unique ID matched then only deserialization will be performed. Otherwise we will get Runtime Exception saying InvalidClassException. This unique Identifier is nothing but SerialVersionUID.

Problem of depending on default SerialVersionUID generated by JVM :

  • Both sender and receiver should use the same JVM with respect to platform and version also. Otherwise receiver unable to deserialize because of different SerialVersionUID.
  • Both sender and receiver should use same .class file version. After serialization if there is any change in .class file at receiver side then receiver unable to deserialize.
  • To generate SerialVersionUID internally JVM may use complex algorithm which may create performance problem.

We can solve the above problem by configuring our own SerialVersionUID. We can configure our own SerialVersionUID as follows :

private static final long SerialVersionUID=1234;

A class Geeks which contains two variable which are going to Serialize

package com.example.java.programming;import java.io.Serializable;/**
* @author code.factory
*
*/
public class CodeFactory implements Serializable {
// User-defined SerialVersionUID
private static final long SerialVersionUID = 1234;
int i = 12;
int j = 34;
}

Program of Sender side which is going to Serialize object

package com.example.java.programming;import java.io.FileOutputStream;
import java.io.ObjectOutputStream;
/**
* @author code.factory
*
*/
public class Sender {
public static void main(String[] args) throws Exception {
CodeFactory cf = new CodeFactory();
// Here xyz.ser is the file name where the object is going to serialize
FileOutputStream fos = new FileOutputStream("xyz.txt");
ObjectOutputStream oos = new ObjectOutputStream(fos);
oos.writeObject(cf);
}
}

Program of Receiver side which is going to deserialize

package com.example.java.programming;import java.io.FileInputStream;
import java.io.ObjectInputStream;
/**
* @author code.factory
*
*/
public class Receiver {
public static void main(String... args) throws Exception {
// Here xyz.ser is the file name where the object is going to Deserialized
FileInputStream fis = new FileInputStream("xyz.txt");
ObjectInputStream ois = new ObjectInputStream(fis);
CodeFactory cf = (CodeFactory) ois.readObject();
System.out.println("Deserialized Object Value : " + cf.i + "..." + cf.j);
}
}

Output :

We can see the file which is xyz.txt where object is Serialize and also the output when we deserialize the Object:

xyz.txt

Run Receiver.java

Deserialized Object Value : 12...34