Additional Notes
Why should we avoid exposing mutable objects through getters?
Track: Java
Topic: OOP
Focus: Access Modifiers and Visibility
Java: Access Modifiers and Visibility
Answer
Exposing mutable objects can lead to unintended modifications.
When a getter returns a reference to a mutable object, external code can modify that object, potentially breaking class invariants. To avoid this, return a copy of the mutable object. For example, a `Customer` class should return a copy of a mutable address object to prevent external changes.
When a getter returns a reference to a mutable object, external code can modify that object, potentially breaking class invariants. To avoid this, return a copy of the mutable object. For example, a `Customer` class should return a copy of a mutable address object to prevent external changes.
Topics: Access Modifiers and Visibility Java OOP