18

Possible Duplicate:
What does it mean: The serializable class does not declare a static final serialVersionUID field?

Java compiler warning: The serializable class [*****] does not declare a static final serialVersionUID field of type long.

Why? How to fix it?

Community
  • 1
  • 1
user496949
  • 83,087
  • 147
  • 309
  • 426

4 Answers4

30

This is explained fairly well here:

The serialVersionUID is a universal version identifier for a Serializable class. Deserialization uses this number to ensure that a loaded class corresponds exactly to a serialized object. If no match is found, then an InvalidClassException is thrown.

You fix the error by adding

private static final long serialVersionUID = 7526472295622776147L;  // unique id

to the class.

Further reading:

A side note: If you're using Eclipse and if you (and no one else) ever plan to serialize your classes, you can also suppress the error by going to

     Window → Preferences → Java → Compiler → Errors/Warnings

and select "Ignore" on "Serializable Class without serialVersionUID".

Community
  • 1
  • 1
aioobe
  • 413,195
  • 112
  • 811
  • 826
6

just add

private static final long serialVersionUID = 1L;//or some long

Docs describe it pretty well

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.

Also See

Community
  • 1
  • 1
jmj
  • 237,923
  • 42
  • 401
  • 438
  • Why downvote ? can you please explain .. – jmj Apr 12 '11 at 08:02
  • I didn't downvote, but perhaps because it is a verbose copy from the source of [Jon Skeets answer](http://stackoverflow.com/questions/285793/why-should-i-bother-about-serialversionuid/285809#285809). – aioobe Apr 12 '11 at 08:07
  • http://download.oracle.com/javase/1.5.0/docs/api/java/io/Serializable.html – jmj Apr 12 '11 at 08:35
1

Declare it like that:

private static final long serialVersionUID = -4673040337179571462L;

Its required by serializable interface.

Lukas
  • 455
  • 4
  • 11
0

Are you extending a Swing object?

I often use the @suppressWarnings annotation to rid myself of this warning.

I guess the question of surpressing the warning or supplying a unique ID depends on the scale of your application and your intended use of Object serialisation.

8bitjunkie
  • 12,793
  • 9
  • 57
  • 70