Without violating encapsulation, capture and externalize an object’s internal state so that the object can be restored to this state later.
Participants
- Memento: stores internal state of the Originator object. The memento may store as much or as little of the originator’s internal state as necessary at its originator’s discretion. Protect against access by objects of other than the originator. Mementos have effectively two interfaces. Caretaker sees a narrow interface to the Memento — it can only pass the memento to the other objects. Originator, in contrast, sees a wide interface, one that lets it access all the data necessary to restore itself to its previous state. Ideally, only the originator that produces the memento would be permitted to access the memento’s internal state.
- Originator: creates a memento containing a snapshot of its current internal state. Uses the memento to restore its internal state
- Caretaker: is responsible for the memento’s safekeeping. Never operates on or examines the contents of a memento.
Code
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 | public class Main { public static void main(String[] args) { Originator o = new Originator(); o.setState("On"); Caretaker c = new Caretaker(); c.setMemento(o.createMemento()); o.setState("Off"); o.setMemento(c.getMemento()); }}public class Originator { private String state; public String getState() { return state; } public void setState(String state) { this.state = state; System.out.println("State = " + state); } public Memento createMemento() { return new Memento(state); } public void setMemento(Memento memento) { System.out.println("Restoring state..."); setState(memento.getState()); }}public class Memento { private String state; public Memento(String state) { this.state = state; } public String getState() { return state; } public void setState(String state) { this.state = state; }}public class Caretaker { private Memento memento; public Memento getMemento() { return memento; } public void setMemento(Memento memento) { this.memento = memento; }} |
Output
1 2 3 4 | State = OnState = OffRestoring state...State = On |
eidherjulian61 / design-patterns
| Published on Java Code Geeks with permission by Eidher Julian, partner at our JCG program. See the original article here: Memento Pattern Opinions expressed by Java Code Geeks contributors are their own. |
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
I agree to the Terms and Privacy Policy
Thank you!
We will contact you soon.
Tags
Design Patterns
👁 Photo of Eidher Julian
Eidher JulianNovember 2nd, 2020Last Updated: October 30th, 2020
Eidher JulianNovember 2nd, 2020Last Updated: October 30th, 2020
2 232 2 minutes read
This site uses Akismet to reduce spam. Learn how your comment data is processed.
A nice variation is to use a stack to push mementos on, that way you can create an Undo mechanism in your application.
You’re right. Thanks for your comment