Abstract Method

Documentation Index

Fetch the complete documentation index at: https://docs.syntblaze.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Syntax

[access_modifier] abstract [return_type] [method_name]([parameters]) [throws ExceptionList];

​

Core Rules and Mechanics

• Enclosing Class Requirement: If a class contains one or more abstract methods, the class itself must be explicitly declared with the abstract keyword. An abstract method cannot exist inside a concrete class.
• Mandatory Overriding: Any concrete (non-abstract) subclass that extends an abstract class must implement all inherited abstract methods. If the subclass fails to implement even one abstract method, the compiler will throw an error unless the subclass is also declared abstract.
• Exception Declaration Rules: If an abstract method declares checked exceptions in its throws clause, the overriding method in the subclass is not required to match it identically. The overriding method can omit the throws clause entirely or declare narrower (subclass) checked exceptions. However, it cannot declare new or broader checked exceptions. Unchecked exceptions (subclasses of RuntimeException) are not enforced by the compiler and can be thrown or declared freely.
• Interface Implicit Abstraction: By default, any method declared in a Java interface without a body is implicitly public and abstract. (Note: Java 8 introduced default and static interface methods, which do possess bodies).
• Illegal Modifier Combinations: The abstract keyword cannot be combined with the following modifiers:
  • private: Private methods are not inherited, making it impossible for a subclass to override and implement them.
  • final: Final methods cannot be overridden, which directly contradicts the purpose of an abstract method.
  • static: Static methods belong to the class rather than the instance and are resolved at compile-time (early binding), preventing polymorphic overriding.
  • native, synchronized, or strictfp: These modifiers require an implementation body or dictate execution behavior that cannot be applied to a method signature alone.

​

Structural Example

import java.io.IOException;

abstract class AbstractBase {
    
    // Abstract method: signature only, no body, includes a checked exception contract
    protected abstract void processData(String input) throws IOException;
    
    // Abstract classes can still contain concrete methods
    public void initialize() {
        System.out.println("Initialization complete.");
    }
}

class ConcreteSubclass extends AbstractBase {
    
    // The compiler mandates this overridden implementation.
    // The throws clause for the checked exception (IOException) can be safely omitted here.
    @Override
    protected void processData(String input) {
        if (input == null) {
            // Unchecked exceptions like IllegalArgumentException do not need to be declared
            throw new IllegalArgumentException("Input cannot be null");
        }
        System.out.println("Processing: " + input);
    }
}