Introduction
In object-oriented programming, class design plays a crucial role in creating robust and maintainable code. With the release of Java 15, a new feature called sealed classes has been introduced, adding an extra layer of control and security to class design. Sealed classes allow developers to restrict class hierarchies, preventing external classes from extending or implementing them. In this article, we will discuss the concept of sealed classes, their benefits, and how they can be implemented in Java.
What are sealed classes?
A sealed class is a new type of class introduced in Java 15, that restricts the inheritance and implementation of its subclasses. It can be considered as a sealed container that allows only specific classes to extend or implement it. Once a class is declared as sealed, it becomes final by default, and any attempt to extend or implement it by external classes will result in a compilation error.
Advantages of using sealed classes
1. Enhanced Security: Sealed classes provide an additional layer of security by restricting the inheritance and implementation of its subclasses. This prevents the unauthorized modification of core classes and ensures that only trusted subclasses can access and modify the sealed class.
2. Better Control over Class Hierarchies: With sealed classes, developers have better control over the class hierarchies. By explicitly defining the allowed subclasses, we can ensure that only relevant and properly designed classes extend or implement the sealed class, leading to a more maintainable codebase.
3. Improved Code Flexibility: By restricting the subclasses that can extend or implement a sealed class, we can make necessary changes or refactoring without worrying about breaking any external code. This provides a sense of flexibility while working with sealed classes and ensures that the codebase remains stable and maintainable.
Implementation of Sealed Classes
To declare a class as sealed, we can use the 'sealed' keyword in the class declaration as shown below:
//Sealed class declaration public sealed class Triangle permits EquilateralTriangle, RightAngleTriangle { //Class body }
Here, the 'permits' keyword is used to specify the subclasses that are allowed to extend the sealed class. In the above example, only the classes 'EquilateralTriangle' and 'RightAngleTriangle' can extend the 'Triangle' class.
Now, let's create the subclasses that can extend the 'Triangle' class.
//Example of Subclass that Extends Sealed Class public final class EquilateralTriangle extends Triangle { //Class body } //Example of Subclass that Extends Sealed Class public non-sealed class RightAngleTriangle extends Triangle { //Class body }
Notice that the 'EquilateralTriangle' class is declared as 'final' since it is the last subclass in the inheritance hierarchy, and the 'RightAngleTriangle' class is declared as 'non-sealed' since it allows further subclasses to extend it.
Next, let's see an example of implementing sealed interfaces. An interface can be declared as sealed using the same syntax as sealed classes.
//Sealed class declaration public sealed class Triangle permits EquilateralTriangle, RightAngleTriangle { //Class body }
Here, the 'permits' keyword is used to specify the classes that are allowed to implement the sealed interface. In the above example, only the classes 'Rectangle' and 'Circle' can implement the 'Shape' interface.
//Example of Subclass that Extends Sealed Class public final class EquilateralTriangle extends Triangle { //Class body } //Example of Subclass that Extends Sealed Class public non-sealed class RightAngleTriangle extends Triangle { //Class body }
Notice that the 'Rectangle' class is declared as 'final' since it is the last class to implement the 'Shape' interface, and the 'Circle' class is declared as 'non-sealed' since it allows further classes to implement it.
Inheritance rules for sealed classes and interfaces
- A sealed class must explicitly permit the subclasses that can extend it.
- All the permitted subclasses must be direct subclasses of the sealed class. This means that we cannot extend a non-permitted subclass to create an indirect subclass of the sealed class.
- A sealed interface must explicitly permit the classes that can implement it.
- All the permitted classes must implement all the interface methods. This means that we cannot create a class that partially implements the sealed interface.
Conclusion
Sealed classes are a powerful addition to Java that can greatly enhance class design and make the codebase more secure and maintainable. By restricting the hierarchy of classes and interfaces, sealed classes provide an additional layer of control and flexibility while designing classes. With this new feature, developers can ensure that only trusted subclasses or implementing classes can access and modify the sealed class, leading to a more stable and robust codebase. Enhance your Java skills by taking latest Java Certifications.
The above is the detailed content of Advanced Class Design using Java Sealed Classes. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.
