Different rules for abstract methods in abstract class and interface

Question

We cannot declare abstract methods in interface as protected and default (even if we don't mention any access specifier (default) compiler takes it as public)

but we can declare abstract method in abstract class as protected and default.

Why there are different rules for abstract class and interface?

Answer 1

Because abstract methods of abstract classes are meant to be hooks for subclasses. On the other hand interfaces are not concerned with implementation details - they are only about contracts with the "outside world". And a protected method is an implementation detail.

Answer 2

we cannot declare abstract methods in interface as protected and defaul

the purpose of Interface is to just declare contract. your client will implement it and for that it must be public .

also field in interface are public static final by default, public you got ,static because it can't be instantiated without implementation and it must not be inherited also.

Update: as per your question

you want to apply some strict constraint which your implementor can't see ..then what is the use of abstract method in abstract class that must be implemented by any concrete class in the inheritance hierarchy...then no one will be concrete class

public class BaseAbstractClass {
  private Connection getConnection(){
      //somecode 

  }

  public boolean save(){
      //get connection and do something 
      //return ;
  }

//your implementor is left to implement it , he  can use save method but can'ge see what it does i mean i doesn't have access to getConnection
  public abstract void saveEntity();

}