Re: Tips: What is the magic Serializable interface does in Java?

Mike Schilling wrote:
Arne Vajh�j wrote:
Persisting object to disk via serialization is usually a bad idea
because of the risk of incompatible changes to the class. Public
or private does not matter.

XML serialization is better because worst the XML files can be
edited (manually or programmatic).

Also because it gives the programmer more control over what's persisted. You can design the bean properties of a serializeable class to contain precisely what you want. And if need be, you can completely re-implement the class while keeping the same set of properties.

These things are true of Serializable serialization as well.