anchor.diff:  
   == Implementation of PmCommand in pm4j ==
   
  -=== Overview ===
  -The PmCommand represents the presentation model of one of the following ui elements:
  -
  -* Buttons
  +=== Class model ===
   
   image:resources/PmCommand_Overview.png[]
  
positive.code:     }
  }
  
  
  === Resource based success message ===
  
  === Testing commands ===
  
  It quite easy to test the implemented functionality of a PmCommand object. To do so you have to create a test conversation for the view that contains your command, first (1).
  Then you can test the implementation of the PMCommand by calling the doIt method (2). To check, if the execution of doIt was successful or not you can validate the CommandState 
  of the PmCommand cmd, now. In our fir test the execution should be successful, so the CommandState should be EXECUTED (3).
  
  When calling the doIt method, it first validates the command like it is descriped in "Validation of a PM area" [HIER LINK SETZEN!]. So it is sometimes required to initialize all 
  the attributes of the parent of your command to prevent a validation error, first (4). But if you want to check that the validation also works fine, you only have to call the doIt method 
  
negative.code: 
  == What is the feature used for ==
  
  PmCommand is an interface to execute actions for e.g. buttons, links or menu entries.
  
  == Usage of PmCommand objects ==
  
  In this chapter we will describe how a framework user can add a new command element. An example for that will be the usage of a button command element.  
  
  === Adding a new PmCommand ===
  
  To use a new command element you have to add the ui element (e.g. commandButton) into the xhtml file and corresponding PmCommand object into the related java implementation.
  
  1. XHTML file:
  [source]
  