The professional, friendly Java community. 21,500 members and growing!

The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.

Serializing an Abstract Class

im not yet well exposed on creating a big architecture for the Inheritance concept when im dealing with big programs, and i came across with this issue, Serializing an Abstract class, consider my codes first
The Base Class(super)

my concern was, when the Super class(ElectronicAppliances) wasnt serializable, and i serialize a Television instance, i wasnt able to include the data members of the SuperClass(voltagetype), i came with the idea that i will serialize the parent class as well,

now my concern is, is this a good practice? ive been searching on google, i even ended up Reading design patterns, but its way too vast to explore for now, i need to clear my mind on this.

- my goal for serializing the abstract super-class was JUST to make its DATA MEMBERS serializable for its sub-classes implementations. i dont intend to write obejcts of the abstract class because as the concept says, abstracts cannot instantiate themselves, i just did it to make the instances of Television class serialize the ElectronicApplicances' data members, am i on the right track?