Why my exception class needs to be serialized?

java exception serialization deserialization serialversionuid
amod picture amod · Oct 7, 2011 · Viewed 22.3k times · Source

When you extend a class with class Exception ( for creating new exception) you get a warning to have a serialVersionUID. I know that serialVersionUID plays an important role while serialization and deserialization, but when my Exception needs to be serialized? Can anyone give me a practical case in which I want my custom-exception class to have serialization and deserialization?

Answer

Sanjay T. Sharma picture Sanjay T. Sharma · Oct 7, 2011

This is because the root class for all exceptions, Throwable implements the Serializable interface. All exceptions by default are serializable and that's a language design decision because the authors wanted exceptions to be capable of being sent across the wire without any special configuration.

If the base class is not serializable, you would have a difficult time conveying what exactly went wrong in case a remote method failed since you would have no control over the built in exception types.

Related questions

Why does writeObject throw java.io.NotSerializableException and how do I fix it?

I have this exception and I don't understand why it would be thrown or, how I should handle it. try { os.writeObject(element); } catch (IOException e) { e.printStackTrace(); } Where element is a TransformGroup containing some other TransformGroups an instance of …

Read More
Java Mysterious EOF exception with readObject

The following code produces an EOFException. Why is that? public static Info readInfoDataFromFile(Context context) { Info InfoData = null; FileInputStream fis = null; ObjectInputStream ois = null; Object object = null; if (context.getFileStreamPath("InfoFile.dat").exists()) { try { fis = context.openFileInput("InfoFile.dat"); ois = …

Read More
How do you assert that a certain exception is thrown in JUnit 4 tests?

How can I use JUnit4 idiomatically to test that some code throws an exception? While I can certainly do something like this: @Test public void testFooThrowsIndexOutOfBoundsException() { boolean thrown = false; try { foo.doStuff(); } catch (IndexOutOfBoundsException e) { thrown = true; } assertTrue(thrown); } I …

Read More