Unit 22 Command

1. Unit 22Command Summary prepared by Kirk Scott

3. Bronze cast of the furcula of "Sue" the Tyrannosaurus, Field Museum

4. Design Patterns in JavaChapter 24Command Summary prepared by Kirk Scott

5. The Introduction Before the Introduction • The ordinary way for a client to cause a method to execute is to call it (on an object), in-line • There may be other times when the client can’t specify exactly when or where a particular method should be called, but would like to be able to pass the method to another piece of code which will call it when needed

6. This can be accomplished by writing a class which contains the desired method • Then at run time an instance of that class can be constructed • That object can have the method called on it • Passing the method can be accomplished by passing the object to another piece of code as an explicit parameter

7. Book definition: • The intent of the Command pattern is to encapsulate a request in an object. • Comment mode on: • Notice that this is what has always happened when writing a class definition and putting a public method in it. • You learned to pass objects as parameters a long time ago, and within receiving code it is possible to call methods on the parameters

8. A Classic Example: Menu Commands • Menus and listeners work together using the Command design pattern • They illustrate the idea that the application writer can’t predict in advance when a user will select a menu item, but can write the code to deal with it when it happens

9. In schematic form, these are the steps in creating a menu in code: • JMenuBarmyMenuBar = new JMenuBar(); • JMenumyMenu = new JMenu(“File”); • myMenuBar.add(myMenu);

10. These steps are followed by the steps for adding items to the menu: • JMenuItemmyExitMenuItem = new JMenuItem(“Exit”); • ExitListenermyExitListener = new ExitListener(); • myExitMenuItem.addActionListener(myExitListener); • myMenu.add(myExitMenuItem);

11. The ExitListener is implemented as an inner class of the frame which has the menu • This is what its code looks like: • private class ExitListener implements ActionListener • { • public void actionPerformed(ActionEvent event) • { • System.exit(0); • } • }

12. The ExitListener class has an actionPerformed() method in it • The actionPerformed() method is executed when the Exit item is clicked in the menu • In the constructor for the frame, where the menu is being created, it is impossible to predict when the Exit item will be clicked • In other words, it is impossible to predict when the actionPerformed() method will be called

13. That’s all right • The following line of code shows how actionPerformed() is linked to the menu item • It is this line of code that illustrates the Command design pattern • myExitMenuItem.addActionListener(myExitListener); • The object myExitListener is passed to myExitItem as an explicit parameter in the call to addActionListener

14. The actionPerformed() method can be called on myExitItem in the future in response to a mouse click on myExitItem • This is mildly cryptic because programmer written code does not contain the call myExitListener.actionPerformed() • The actual call is made by the system through Java’s event handling mechanism • Even so, the Command design pattern is evident in the way the item and the listener are linked

15. The book notes that once again, polymorphism is at work in the way menus function • Each menu item can have a different listener which takes different actions • Each listener has a method with the same name, actionPerformed()

16. Which action is performed depends on which kind of listener the system calls actionPerformed() on • The system only needs to know that in each case, actionPerformed() should be called, and polymorphism makes sure that the right action is taken for each different kind of listener

17. In CS 202, for example, event handling is simply described as the system calling the actionPerformed() method • It is important to note that the system calls the actionPerformed() method on the listener object • The system has access to the objects that are declared as listeners in a program

18. Menu Commands and the Mediator Pattern • Challenge 24.1 • The mechanics of Java menus make it easy to apply the Command pattern but do not require that you organize your code as commands. • In fact, it is common to develop an application in which a single object listens to all the events in a GUI. • What pattern does that follow?

19. Comment mode on: • This may be an interesting question, but the authors are spinning out into space now • This question is unrelated to understanding the design pattern in question.

20. Solution 24.1 • Many Java Swing applications apply the Mediator pattern, registering a single object to receive all GUI events. • This object mediates the interaction of the components and translates user input into commands for business domain objects.

21. Notice that the approach just described could be a mess to implement for menus and it could be equally messy for other situations • If you had a single listener for all menu items, the contents of the actionPerformed() method would degenerate into a series of if/else statements

22. These if/elses would have to determine which item had been clicked • Their bodies would consist of blocks of code implementing the appropriate actions • Notice how this is exactly the opposite of having many different listeners and relying on polymorphism and dynamic binding to take care of which action to take

23. The Command and Strategy Patterns • If you think back to the Strategy design pattern, for example, that was the kind of mess you were hoping to avoid • Instead of having if/else code, the solution was to have different classes for each strategy (in this case, each menu item) • Each class would have a method with the same name but containing the implementation of a different strategy (in this case, a different action to be performed)

24. In other words, the handling of menus in Java exhibits the characteristics of two design patterns • The fact that there are different listener classes, each with an actionPerformed() method illustrates the Strategy design pattern • The fact that listeners are added to items so that their actionPerformed() method can be called in the future when needed illustrates the Command design pattern

25. Recall also, that with the Strategy design pattern you ended up with lots of little classes, each containing just a single method, and which you only needed one instance of • The same thing happens with (standard) menus • There is a different kind of listener for each menu item • Each listener just contains an implementation of actionPerformed() • Only one instance of each listener is needed

26. Anonymous Classes • The book observes that this is the kind of situation where anonymous classes can be used • I still don’t like anonymous classes, but it is important to get used to them because other programmers use them • Recall that in CS 202, it was also a listener which was used as an anonymous class example

27. The book next presents code with the anonymous listeners missing • It is not reproduced here because it is immediately followed by a challenge to fill in the missing listeners • It’s easier to just go directly to the complete example with all of the pieces included

28. Challenge 24.1 • Fill in the code for the anonymous subclasses of ActionListener, overriding the actionPerformed() method. Note that this method expects an ActionEvent argument.

29. Solution 24.2 • Your code should look something like this: • Comment mode on: • In the book, the solution code is followed by some additional remarks • Instead of putting them at the end, they are given up front here, followed by a comment on them, followed by the code

30. Book’s remarks on the solution code: • Although the actionPerformed() method requires an ActionEvent argument, you can safely ignore it. • The menus() method registers a single instance of an anonymous class with the Save menu item and a single instance of another anonymous class with the Load menu item. • When these methods are called, there is no doubt about the source of the event.

31. Comment mode on: • There are two things to say about this: • First of all, the book’s statement forewarns us that the creation of the menu in the solution code occurs in a separate method in the application, named menus()

32. Secondly, there is nothing new in the remarks about the ActionEvent parameter • We have always ignored it when writing menu listeners • We’ve seen examples in CS 202 where the event parameter is of interest • For example, it was necessary to get the (x, y) coordinates of a mouse click to see if it occurred in a cup • But quite often, there has been no need to do anything with the event parameter in a listener

33. The book’s solution code is given on the following overheads • Keep in mind the purpose of the challenge and the code shown • It is to illustrate how menu listeners (in this case, anonymous ones) make use of the Command design pattern

34. public class Visualization2 extends Visualization { • public static void main(String[] args) • { • Visualization2 panel = new Visualization2(UI.NORMAL); • JFrame frame = SwingFacade.launch(panel, "Operational Model"); • frame.setJMenuBar(panel.menus()); • frame.setVisible(true); • } • public Visualization2(UI ui) • { • super(ui); • }

35. public JMenuBar menus() • { • JMenuBarmenuBar = new JMenuBar(); • JMenu menu = new JMenu("File"); • menuBar.add(menu); • JMenuItemmenuItem = new JMenuItem("Save As..."); • menuItem.addActionListener(new ActionListener() • { • public void actionPerformed(ActionEvent e) • { • save(); • } • }); • menu.add(menuItem); • menuItem = new JMenuItem("Restore From..."); • menuItem.addActionListener(new ActionListener() • { • public void actionPerformed(ActionEvent e) • { • restore(); • } • }); • menu.add(menuItem); • return menuBar; • }

36. public void save() • { • try • { • mediator.save(this); • } • catch (Exception ex) • { • System.out.println("Failed save: " + ex.getMessage()); • } • } • public void restore() • { • try • { • mediator.restore(this); • } • catch (Exception ex) • { • System.out.println("Failed restore: " + ex.getMessage()); • } • } • }

37. Using Command to Supply a Service • In the previous example, half the work was done by the Java API • All that was necessary was to plug a command into an existing context • In other words, the addActionListener() machinery is provided by the API • It is also possible for a programmer to provide both the context and the command

38. The Next Example • The next example shows how to time how long it takes to execute some method, methodA() • There will be a timing method, methodB(), that takes as its input parameter an object which can have methodA() called on it • Inside methodB() the call to methodA() on the input parameter will be sandwiched between timing code

39. Setting up the Command to be Passed • Let there be an abstract class named Command which includes this abstract method declaration: • public abstract void execute(); • A concrete command class would extend Command and implement execute() • The abstract method, execute(), defines the interface for using a command object

40. Setting up the Code that will Receive the Command • In addition to a concrete command class, the example includes a class named CommandTimer • This class contains a static method named time() • The time() method takes as an input parameter an instance of a command class • execute() is called on that command class object in the body of the time() method

41. Calls to methods that make it possible to keep track of the passage of time can be placed before and after the call to execute() in the time() method • Code for the CommandTimer class and its time() method are given on the next overhead • Keep in mind that the method is static.

42. public class CommandTimer • { • public static long time(Command command) • { • long t1 = System.currentTimeMillis(); • command.execute(); • long t2 = System.currentTimeMillis(); • return t2 – t1; • } • }

43. The book next presents code to test the setup, with the call that causes the execution missing • The code with the missing step is not reproduced here because it is immediately followed by a challenge to fill in the missing line of code • It’s easier to just go directly to the complete example with all of the pieces included

44. The authors are trying to illustrate the use of a JUnit test framework • This is mentioned in Appendix C, on the source code, and also at various points in the text • You don’t have to worry about it • It just adds a little stuff at the end of the example code which you can ignore • They also use the anonymous class syntax when creating the command

45. Challenge 24.3 • Complete the assignment statement that sets the value for actual in such a way that the doze command is timed.

46. Solution 24.3 • The testSleep() method passes the doze command to the time() utility method. • Comment mode on: • The code creates an instance of Command, named doze • It then calls the static time() method, passing doze as a parameter • See the code on the next overhead.

47. public class TestCommandTimer extends TestCase • { • public void testSleep() • { • Command doze = new Command() • { • public void execute() • { • try • { • Thread.sleep(2000 + Math.round(10 * Math.random())); • } • catch (InterruptedException ignored) • { • } • } • }; • long actual = CommandTimer.time(doze); • long expected = 2000; • long delta = 5; • assertTrue("Should be " + expected + " +/- " + delta + " ms", • expected - delta <= actual • && actual <= expected + delta); • } • }

48. The point of the foregoing example code was that it created an object of the Command class named doze • This object contained an execute() method that caused it to sleep for a random amount of time • The line of code shown below made use of the command machinery given previously to time how long it takes for doze.execute() to run • long actual = CommandTimer.time(doze);

49. Command Hooks • This section builds on material that was presented in the chapter on the Template Method • You may recall that in that chapter I restricted myself to the discussion of sorting as implemented in the Java API • I did not pursue the other examples • Therefore, it is not possible to pursue this example in this chapter • You are not responsible for it

50. Command in Relation to Other Patterns • The book states that command is similar to a pattern in which a client knows when an action is required but doesn’t know exactly which operation to call. • This may be true, but this is not exactly what the examples in this chapter have illustrated.