Final Class in Java: Enforcing Immutability and Security

A final class in Java is a class that cannot be extended (inherited). By declaring a class as final, you prevent other classes from subclassing it, ensuring its behavior remains unchanged. In this guide, you’ll learn how to use final classes, their benefits, and practical examples to secure your code.

What is a Final Class in Java?

A final class is declared using the final keyword:

public final class String { // java.lang.String is a final class  
    // Class implementation  
}  

Key Characteristics:

• Cannot be subclassed: Any attempt to extend it causes a compile-time error.
• Methods are implicitly final: Cannot be overridden (since the class itself can’t be extended).

Why Use a Final Class?

1. Security: Prevent malicious or accidental subclassing (e.g., overriding methods to alter behavior).
2. Immutability: Ensure critical classes like String remain unmodifiable.
3. API Design: Lock down class behavior in libraries/frameworks.
4. Performance: Some JVM optimizations apply to final classes.

Example: Declaring and Using a Final Class

1. Define a Final Class

public final class Logger {  
    public void log(String message) {  
        System.out.println("[LOG] " + message);  
    }  
}  

2. Attempting to Extend (Error)

// Compiler Error: Cannot inherit from final Logger  
class CustomLogger extends Logger {  
    // ❌ Not allowed!  
}  

Final Class vs. Final Method vs. Final Variable

Best Practices

1. Use Sparingly: Finalize only classes critical to security/immutability.
2. Combine with Private Constructors: For utility classes (prevent instantiation).
3. Document Reasons: Clarify why a class is final (e.g., “Security: prevent tampering”).
4. Consider Alternatives: Use encapsulation or interfaces if extensibility is needed.

Conclusion

Final class in Java are essential for designing secure, immutable, and stable APIs. By preventing inheritance, they safeguard critical logic from unintended modifications. Use them judiciously to balance flexibility and control.

FAQs