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.
Add a comment
|
2 Answers
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).
1 Comment
Mike Warren
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).
The constructor/getters/setters are not mandatory. Non-transient collections although serializable containing references to non-serializable objects will cause failures.
