CS 635 Advanced Object-Oriented Design & Programming Spring Semester, 2001 Memento, Command, Command Processor
	Previous    Lecture Notes Index    Next     © 2001, All Rights Reserved, SDSU & Roger Whitney San Diego State University -- This page last updated 21-Mar-01

Memento

Structure
Applicability
Consequences/ Implementation
Iterators & Mementos

Command

Structure
When to Use the Command Pattern
Consequences

Command Processor

Structure
Consequences

Doc 11, Memento, Command, Command Processor Slide # 2

Memento

Structure

• Can access Memento’s get/set state methods

• Create Memento

Doc 11, Memento, Command, Command Processor Slide # 3

Applicability

• Need to save all or part of the state of an object and

• Do not wish to expose the saved state to the outside world

Doc 11, Memento, Command, Command Processor Slide # 4

package Examples;
class Memento
   {
   private Hashtable savedState = new Hashtable();
   
   protected Memento() {}; //Give some protection
   
   protected void setState( String stateName, Object stateValue )
      { 
      savedState.put( stateName, stateValue );
      } 
   protected Object getState( String stateName)
      {
      return savedState.get( stateName);
      } 
      
   protected Object getState(String stateName, Object defaultValue )
      {
      if ( savedState.containsKey( stateName ) )
         return savedState.get( stateName);
      else
         return defaultValue;
      } 
   }

Doc 11, Memento, Command, Command Processor Slide # 5

package Examples;
class ComplexObject
   {
   private String name;
   private int someData;
   private Vector objectAsState = new Vector();
   
   public Memento createMemento()
      {
      Memento currentState = new Memento();
      currentState.setState( "name", name );
      currentState.setState( "someData", new Integer(someData) );
      currentState.setState( "objectAsState", objectAsState.clone() );
      return currentState;
      }
   
   public void restoreState( Memento oldState)
      {
      name = (String) oldState.getState( "name", name );
      objectAsState = (Vector) oldState.getState( "objectAsState" );
      Integer data = (Integer) oldState.getState( "someData");
      someData = data.intValue();
      }

Doc 11, Memento, Command, Command Processor Slide # 6

   // Show a way to do incremental saves
   public Memento setName( String aName )
      {
      Memento deltaState = saveAState( "name", name);
      name = aName;
      return deltaState;
      }

   public void setSomeData( int value )
      {
      someData = value;
      }
   private Memento saveAState(String stateName, Object stateValue)
      {
      Memento currentState = new Memento();
      currentState.setState( stateName, stateValue );
      return currentState;
      }   
   }

Doc 11, Memento, Command, Command Processor Slide # 7

Consequences/ Implementation

How to store state history and for how long?

Doc 11, Memento, Command, Command Processor Slide # 8

Make Memento's interface private

Make Originator a friend of the Memento

   Class Memento {
   public:
      virtual ~Memento();
   private:
      friend class Originator;
      Memento();
      void setState(State*);
      State* GetState();
      ...

Doc 11, Memento, Command, Command Processor Slide # 9

Use private nested/inner class to hide memento's interface

class ComplexObject {
   private String name;
   private int someData;
   
   public Memento createMemento() {
      return new Memento();
   }
      
   public void  restoreState( Memento oldState) {
      oldState.restoreStateTo( this );
   }
   
   public class Memento {
      private String savedName;
      private int savedSomeData;
      
      private Memento() {
         savedName = name;
         savedSomeData = someData;
      }
      
      private void restoreStateTo(ComplexObject target) {
         target.name = savedName;
         target.someData = savedSomeData;
      }
   }
}

Doc 11, Memento, Command, Command Processor Slide # 10

interface Memento extends Cloneable { }

class ComplexObject implements Memento {
   private String name;
   private int someData;
   
   public Memento createMemento() {
      Memento myState = null;
      try {
         myState =  (Memento) this.clone();
      }
      catch (CloneNotSupportedException notReachable) {
      }
      return myState;
   }
      
   public void  restoreState( Memento savedState) {
      ComplexObject myNewState = (ComplexObject)savedState;
      name = myNewState.name;
      someData = myNewState.someData;
   }
}

Doc 11, Memento, Command, Command Processor Slide # 11

Iterators & Mementos

class IteratorState {
   int currentPosition = 0;
   
   protected IteratorState() {}
   
   protected int getPosition() {   return currentPosition;   }
   
   protected void advancePosition() { currentPosition++; }
   }
   
class Vector {
   protected Object elementData[];
   protected int elementCount;
   
   public IteratorState newIteration() { return new IteratorState(); }
   
   public boolean hasMoreElements(IteratorState aState) {
      return aState.getPosition() < elementCount;
   }
   
   public Object nextElement( IteratorState aState ) {
      if (hasMoreElements( aState ) ) {
         int currentPosition = aState.getPosition();
         aState.advancePosition();
         return elementData[currentPosition];
         }
   throw new NoSuchElementException("VectorIterator");
   }
   ...

Doc 11, Memento, Command, Command Processor Slide # 12

Command

Structure

Invoker be a menu

Client be a word processing program

Receiver a document

Action be save

Doc 11, Memento, Command, Command Processor Slide # 13

When to Use the Command Pattern

• When you need an action as a parameter

Commands replace callback functions

• When you need to specify, queue, and execute requests at different times

• When you need to support undo

• When you need to support logging changes

• When you structure a system around high-level operations built on primitive operations

A Transactions encapsulates a set of changes to data

Systems that use transaction often can use the command pattern

• When you need to support a macro language

Doc 11, Memento, Command, Command Processor Slide # 14

Consequences

Doc 11, Memento, Command, Command Processor Slide # 15

abstract class Command
   {
   abstract public void execute();
   }
   
class OpenCommand extends Command
   {
   private Application opener;
   
   public OpenCommand( Application theOpener )
      {
      opener = theOpener;
      }
   
   public void execute()
      {
      String documentName = AskUserSomeHow();
      
      if ( name != null )
         {
         Document toOpen = 
               new Document( documentName );
         opener.add( toOpen );
         opener.open();
         }
      }
   }

Doc 11, Memento, Command, Command Processor Slide # 16

class Menu
   {
   private Hashtable menuActions = new Hashtable();
   
   public void addMenuItem( String displayString, 
                  Command itemAction )
      {
      menuActions.put( displayString, itemAction );
      }
   public void handleEvent( String itemSelected )
      {
      Command runMe;
      runMe = (Command) menuActions.get( itemSelected );
      runMe.execute();
      }
   // lots of stuff missing
   }

Doc 11, Memento, Command, Command Processor Slide # 17

class MacroCommand extends Command
   {
   private Vector commands = new Vector();
   
   public void add( Command toAdd )
      {
      commands.addElement( toAdd );
      }
   
   public void remove( Command toRemove )
      {
      commands.removeElement( toAdd );
      }
   
   public void execute()
      {
      Enumeration commandList = commands.elements();
      
      while ( commandList.hasMoreElements() )
         {
         Command nextCommand;
         nextCommand = (Command)
                      commandList.nextElement();
         nextCommand.execute();
         }
      }
   }

Doc 11, Memento, Command, Command Processor Slide # 18

import java.util.*;
import java.lang.reflect.*;

public class Command
   {
   private Object receiver;
   private Method command;
   private Object[] arguments;
   
   public Command(Object receiver, Method command, 
                           Object[] arguments )
      {
      this.receiver = receiver;
      this.command = command;
      this.arguments = arguments;
      }
   public void execute() throws InvocationTargetException, 
                                 IllegalAccessException
      {
      command.invoke( receiver, arguments );
      }
   }
Doc 11, Memento, Command, Command Processor Slide # 19

public class Test {
   public static void main(String[] args) throws Exception 
      {
      Vector sample = new Vector();
      Class[] argumentTypes = { Object.class };
      Method add = 
         Vector.class.getMethod( "addElement", argumentTypes);
      Object[] arguments = { "cat" };
      
      Command test = new Command(sample, add, arguments );
      test.execute();
      System.out.println( sample.elementAt( 0));
      }
   }

Doc 11, Memento, Command, Command Processor Slide # 20

Object subclass: #PluggableCommand
   instanceVariableNames: 'receiver selector arguments '
   classVariableNames: ''
   poolDictionaries: ''
   category: 'Whitney-Examples'

receiver: anObject selector: aSymbol arguments: anArrayOrNil
   ^super new
      setReceiver: anObject 
      selector: aSymbol 
      arguments: anArrayOrNil

setReceiver: anObject selector: aSymbol arguments: anArrayOrNil
   receiver := anObject.
   selector := aSymbol.
   arguments := anArrayOrNil isNil
               ifTrue:[#( )]
               ifFalse: [anArrayOrNil]

execute
   ^receiver 
      perform: selector 
      withArguments: arguments

Doc 11, Memento, Command, Command Processor Slide # 21

| sample command |
sample := OrderedCollection new.
command := PluggableCommand
      receiver: sample
      selector: #add:
      arguments: #( 5 ).
command execute.
^sample at: 1

Doc 11, Memento, Command, Command Processor Slide # 22

Command Processor

• Contains all command objects

• Schedules the execution of commands

• May store the commands for later unto

• May log the sequence of commands for testing purposes

• Uses singleton to insure only one instance

Doc 11, Memento, Command, Command Processor Slide # 23

Structure

Doc 11, Memento, Command, Command Processor Slide # 24

Consequences

• Flexibility in the way requests are activated

Different user interface elements can generate the same kind of command object

Allows the user to configure commands performed by a user interface element

• Flexibility in the number and functionality of requests

Adding new commands and providing for a macro language comes easy

• Programming execution-related services

Commands can be stored for later replay

Commands can be logged

Commands can be rolled back

• Testability at application level

• Concurrency

Allows for the execution of commands in separate threads

Doc 11, Memento, Command, Command Processor Slide # 25

• Efficiency loss

• Potential for an excessive number of command classes

Try reducing the number of command classes by:

Grouping commands around abstractions

Unifying simple commands classes by passing the receiver object as a parameter

• Complexity

How do commands get additional parameters they need?

Doc 11, Memento, Command, Command Processor Slide # 26

Previous    visitors since 21-Mar-01    Next