1

Every example I have seen regarding object serialization, includes an all field constructor and a getter and setter method for every field. Is this nessecary? What do you have to do to make a java object serializable, other tagging it with the serializable interface and assuring all non-transient field are them selves serializable.

rubixibuc
  • 7,111
  • 18
  • 59
  • 98

2 Answers2

4

There is nothing required to make an Object serializable, apart from the basic steps you've mentioned. There are no requirements for the existence of getters/setters or constructors of a certain form (though there may be other legitimate reasons to want those).

VeeArr
  • 6,039
  • 3
  • 24
  • 45
  • 1
    Think of getters as a secure way to obtain needed information from your Objects, and setters a good idea in case you need to modify any of it (for whatever reason). – Mike Warren Jun 08 '13 at 23:32
2

The constructor/getters/setters are not mandatory. Non-transient collections although serializable containing references to non-serializable objects will cause failures.

Java42
  • 7,628
  • 1
  • 32
  • 50