Why can't overriding methods throw exceptions broader than the overridden method?

Question

I was going through SCJP 6 book by Kathe sierra and came across this explanations of throwing exceptions in overridden method. I quite didn't get it. Can any one explain it to me ?

The overriding method must NOT throw checked exceptions that are new or broader than those declared by the overridden method. For example, a method that declares a FileNotFoundException cannot be overridden by a method that declares a SQLException, Exception, or any other non-runtime exception unless it's a subclass of FileNotFoundException.

Answer 1

It means that if a method declares to throw a given exception, the overriding method in a subclass can only declare to throw that exception or its subclass. For example:

class A {    public void foo() throws IOException {..} }  class B extends A {    @Override    public void foo() throws SocketException {..} // allowed     @Override    public void foo() throws SQLException {..} // NOT allowed } 

SocketException extends IOException, but SQLException does not.

This is because of polymorphism:

A a = new B(); try {     a.foo(); } catch (IOException ex) {     // forced to catch this by the compiler } 

If B had decided to throw SQLException, then the compiler could not force you to catch it, because you are referring to the instance of B by its superclass - A. On the other hand, any subclass of IOException will be handled by clauses (catch or throws) that handle IOException

The rule that you need to be able to refer to objects by their superclass is the Liskov Substitution Principle.

Since unchecked exceptions can be thrown anywhere then they are not subject to this rule. You can add an unchecked exception to the throws clause as a form of documentation if you want, but the compiler doesn't enforce anything about it.