

is a serializable object (that is, it implements java.io.Serializable, and does so correctly), that.The reality is nowhere near so mysterious. There's a term for it to make it sound special. For example, if a library wants to stream any object you pass into it, it knows it can because your object is serializable (assuming the library requires your objects be proper JavaBeans). There is a term for it, because the standard allows libraries to programmatically do things with class instances you define in a predefined way. In other words, serializable objects can be written to streams, and hence files, object databases, anything really.Īlso, there is no syntactic difference between a JavaBean and another class - a class is a JavaBean if it follows the standards. Identify the semantics of being serializable. Serialization interface has no methods or fields and serves only to

Interface will not have any of their state serialized or deserialized.Īll subtypes of a serializable class are themselves serializable. Serializability of a class is enabled by the class implementing the

With respect to Serializable, from the API documentation: All properties are private (use getters/setters).It is a regular Java class, except it follows certain conventions:
