The CoffeeMachine ExampleĮncapsulation was used when the CoffeeMachine class example was created. You bundle a set of attributes that store the current state of the object with a set of methods using these attributes. In essence, it’s simply how you design a Java class. It’s a basic concept that most Java developers use without a lot of thought. If you’ve read our previous post about abstraction, you already saw several examples for encapsulation. This example implements information hiding and applies additional validation before changing the values of your object attributes. Let’s take a look at an example that shows the concept of encapsulation in Java. Later, we’ll show you how the setter method can also be used to implement additional validation rules to ensure that your object always has a valid state. You may also control if the attribute is read-only or not visible at all. Depending on the methods that you implement, you can decide if an attribute can be read and changed. As the names indicate, a getter method retrieves an attribute and a setter method changes it. If you’re familiar with any object-oriented programming language, you probably know these methods as getter and setter methods. Encapsulation allows you to hide specific information and control access to the internal state of the object. You bundle it with methods that provide read or write access. For example, you have an attribute that is not visible from the outside of an object. The general idea of this mechanism is simple. This concept is also often used to hide the internal representation, or state of an object from the outside. Let’s examine how it’s done and unwrap some examples for this concept.īy definition, encapsulation describes the idea of bundling data and methods that work on that data within one unit, like a class in Java. Encapsulation is one of the fundamental concepts in object-oriented programming (OOP).
0 kommentar(er)
