The problem in general is that it is sometimes unclear from books why do we need some particular technology. In this case we are going to discuss why do you need inheritance and where it is used in real-life applications.
Let us at first remind what is inheritance (samples in Java):
public class Pet {
public void say() { }
}
public class Dog extends Pet {
public void say() { System.out.println("I am a dog."); }
}
public class Cat extends Pet {
public void say() { System.out.println("I am a cat."); }
}
public class Test{
public static void main(String[] args) {
Pet pet1 = new Dog();
Pet pet2 = new Cat();
pet1.say();
pet2.say();
}
}
This programm will output:
I am a dog.
I am a cat.
The idea is very simple: despite pet1 and pet2 are of type Pet, pet1 is pointing to object of class Dog and pet is pointing to object of class Cat.
The common question which is usually raised is: why we don’t have just Dog pet1 = new Dog(); and Cat pet2 = new Cat(); ? Whe do we need to access it via Pet?
Let me give you some real-world examples where do we need it:
1. Servlets. When we create a servlet we inherit base servlet class and override method doGet() or doPost()to add our functionality to the servlet. The server (for example Tomcat) have list of our servlet classes deployed, and as soon as it gets request for our servlet it loads our class, create an object and call doGet() or doPost() on it. As soon as server have no idea what classes do we have it address object of our class via variable of type HttpServlet.
2. The similar idea was used in early versions of Struts library.
3. In .NET as well as in Java you override Exception class or one of it’s successors to create exception specific to your application. The system (Java or .NET) knows only how to work with Exception (and RuntimeException specificly in Java) and works with all your exceptions uniformaly.
