Memento Design Pattern

Intent

Without violating encapsulation, capture and externalize an objects internal state so that the object can be restored to this state later.
One of the best real-life example is the text editors where we can save its data anytime and use undo to restore it to previous saved state. 

Also Known As

Token

Structure


Participants

1. Memento 
  • This component 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.
  • This component protects against access by objects other than the originator. Mementos have effectively two interfaces. Caretaker sees a narrow interface to the Memento�it can only pass the memento to 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 produced the memento would be permitted to access the memento's internal state.
2. Originator
  • This component creates a memento containing a snapshot of its current internal state.
  • This component uses the memento to restore its internal state.
3. Caretaker 
  • It is responsible for the memento's safekeeping.
  • It never operates on or examines the contents of a memento

Source code

Memento pattern is implemented with two objects � Originator and Caretaker. The Originator is the object whose state needs to be saved and restored and it uses an inner class to save the state of Object. The inner class is called Memento and its private so that it can�t be accessed from other objects.
Caretaker is the helper class that is responsible for storing and restoring the Originator�s state through Memento object. Since Memento is private to Originator, Caretaker can�t access it and it�s stored as an Object within the caretaker.
Step 1: Let's create Originator Class.
public class FileWriterUtil {
 private String fileName;
 private StringBuilder content;
 public FileWriterUtil(String file) {
  this.fileName = file;
  this.content = new StringBuilder();
 }

 @Override
 public String toString() {
  return this.content.toString();
 }
 public void write(String str) {
  content.append(str);
 }
 public Memento save() {
  return new Memento(this.fileName, this.content);
 }
 public void undoToLastSave(Object obj) {
  Memento memento = (Memento) obj;
  this.fileName = memento.fileName;
  this.content = memento.content;
 }
 private class Memento {
  private String fileName;
  private StringBuilder content;
  public Memento(String file, StringBuilder content) {
   this.fileName = file;
   //notice the deep copy so that Memento and FileWriterUtil
   content variables don 't refer to same object
   this.content = new StringBuilder(content);
  }
 }
}
Notice the Memento inner class and implementation of save and undo methods. Now we can continue to implement Caretaker class.
Step 2: Create Caretaker Class.
public class FileWriterCaretaker {
 private Object obj;

 public void save(FileWriterUtil fileWriter) {
  this.obj = fileWriter.save();
 }
 
 public void undo(FileWriterUtil fileWriter) {
  fileWriter.undoToLastSave(obj);
 }
 
}
Notice that caretaker object contains the saved state in the form of Object, so it can�t alter its data and also it has no knowledge of its structure.
Step 3: Let's test Memento design pattern.Let�s write a simple test program that will use our memento implementation.
public class FileWriterClient {
 public static void main(String[] args) {
  FileWriterCaretaker caretaker = new FileWriterCaretaker();
  FileWriterUtil fileWriter = new FileWriterUtil("data.txt");
  fileWriter.write("First Set of Data\n");
  System.out.println(fileWriter + "\n\n");
  // lets save the file
  caretaker.save(fileWriter);
  //now write something else
  fileWriter.write("Second Set of Data\n");
  //checking file contents
  System.out.println(fileWriter + "\n\n");
  //lets undo to last save
  caretaker.undo(fileWriter);
 }

Applicability

Use the Memento pattern when
  • a snapshot of an object's state must be saved so that it can be restored to that state later, and
  • a direct interface to obtaining the state would expose implementation details and break the object's encapsulation

Real world examples

Comments

Post a Comment

Popular posts from this blog

Design Patterns used in Hibernate Framework

Image
In this post, let's discuss a different kind of design patterns which are widely used in the Hibernate Framework. Design Patterns denote the best computer programming practices in the object-oriented software development. Hibernate framework has been built by using the following design pattern or standard practices. I list few known design patterns used in Hibernate Framework. Please mention in a comment, if you know any other design patterns used in Hibernate Framework. You can also read my post of  Design Patterns used in Spring Framework Domain Model Pattern The domain model is treated as POJO in Hibernate. The domain model is an object model of the domain that incorporates both behavior and data. Read more about Domain Model Pattern here https://stackoverflow.com/questions/41335249/domain-model-pattern-example Proxy Design Pattern Proxy Pattern for lazy loading - https://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.html Proxy Pattern provides a surrogate or pl
Read more

Data Mapper Pattern

Image
This pattern belongs to  Data Source Architectural Patterns  Catalog and this Catalog belongs to  Patterns of Enterprise Application Architecture . Intent A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself. Mapper means an object that sets up a communication between two independent objects. Applicability Use the Data Mapper in any of the following situations when you want to decouple data objects from DB access layer when you want to write multiple data retrieval/persistence implementations Explanation The Data Mapper is a layer of software that separates the in-memory objects from the database. Its responsibility is to transfer data between the two and also to isolate them from each other.  With Data Mapper the in-memory objects needn't know even that there's a database present; they need no SQL interface code, and certainly no knowledge of the database schema.  How It Works The separation betwee
Read more

Information Expert GRASP Pattern

Image
Information Expert is the  GRAS Patterns (General Responsibility Assignment Software Pattern) Read about GRASP Patterns:  GRASP Patterns Overview Problem What is a general principle of assigning responsibilities to objects? A Design Model may define hundreds or thousands of software classes, and an application may require hundreds or thousands of responsibilities to be fulfilled. During object design, when the interactions between objects are defined, we make choices about the assignment of responsibilities to software classes. Done well, systems tend to be easier to understand, maintain, and extend, and there is more opportunity to reuse components in future applications. Solution Assign a responsibility to the information expert - the class that has the information necessary to fulfill the responsibility. Example   Let's consider Point of Sale (POS) application: a Brief overview of POS application. Application for a shop, restaurant, etc. that registers sales. Each sale is of one
Read more