Java Seralization and Deseralization

Question

I have an object as follows:

    public class Records implements java.io.Serializable{
        private int cId;
        private int pId;
        private int vlaue;
        private int tag;

        public Records(int c, int p, int v, int t){
                this.cId=c;
                this.pId=p;
                this.value=v;
                this.tag=t;
        }
}

I've collected lots of data, constructed objects as in the above class and seralized them to disk.

One dump thing I've forgotten to include in the class file is methods to access the values for each object. For example, to access the cId value for a particular object.

I modified the class definition to add such methods but then I could not deseralize the objects back to Records class and get this runtime error:

java.io.InvalidClassException: Records; local class incompatible: stream classdesc serialVersionUID = -1232612718276774474, local class serialVersionUID = -8244963718951538904
    at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:579)
    at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1600)
    at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1513)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1749)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
    at DeSerialise.main(DeSerialise.java:21)

I think I need to tell java that they are the same definitions and modify the serialVersionUID but not quite sure how? any idea would be welcomed!

Answer 1

Try adding the following to your class:

private static final long serialVersionUID = -1232612718276774474L;

That'll bring your class's serialVersionUID in line with the compiler-generated value used when the instance was serialized.

The following quote from the documentation is worth reading (emphasis mine):

The serialization runtime associates with each serializable class a version number, called a serialVersionUID, which is used during deserialization to verify that the sender and receiver of a serialized object have loaded classes for that object that are compatible with respect to serialization. If the receiver has loaded a class for the object that has a different serialVersionUID than that of the corresponding sender's class, then deserialization will result in an InvalidClassException. A serializable class can declare its own serialVersionUID explicitly by declaring a field named "serialVersionUID" that must be static, final, and of type long:

ANY-ACCESS-MODIFIER static final long serialVersionUID = 42L;

If a serializable class does not explicitly declare a serialVersionUID, then the serialization runtime will calculate a default serialVersionUID value for that class based on various aspects of the class, as described in the Java(TM) Object Serialization Specification. However, it is strongly recommended that all serializable classes explicitly declare serialVersionUID values, since the default serialVersionUID computation is highly sensitive to class details that may vary depending on compiler implementations, and can thus result in unexpected InvalidClassExceptions during deserialization. Therefore, to guarantee a consistent serialVersionUID value across different java compiler implementations, a serializable class must declare an explicit serialVersionUID value. It is also strongly advised that explicit serialVersionUID declarations use the private modifier where possible, since such declarations apply only to the immediately declaring class--serialVersionUID fields are not useful as inherited members. Array classes cannot declare an explicit serialVersionUID, so they always have the default computed value, but the requirement for matching serialVersionUID values is waived for array classes.

Answer 2

Yes its very important that you specify serialversionId for class. Otherwise it will be difficult to identify serialized class.

You can also create new serialized object instead of using old serialized object if you are doing so.

Eclipse IDE will automatically generate serialversionId try to use that.

Answer 3

The problem is that you serialized data without having a serialVersionUID defined in your class. Adding setters and getters is ok and does not impact serialization, but the compiler might generate another UID when you recompile the class which will lead to an exception when you try to deserialize your data. If need to actually deserialize the data you serialized using the first version of your class you will need to know what UID was generated by the compiler the first time: this can be seen in the error message, so you need to set serialVersionUID to -1232612718276774474L.

Answer 4

You can declare the serial version id in your class as follows:

private static final long serialVersionUID = -1232612718276774474L;