public class RestoreHistoryCommand extends RevertNodeCommand implements HistoryGeneratingCommand
| Constructor and Description | 
|---|
RestoreHistoryCommand()  | 
| Modifier and Type | Method and Description | 
|---|---|
int | 
doit()
Executes the actions associated with the revert command to revert the
 specified node. 
 | 
Node[] | 
getHistoriedNodes()
Get an array of Node whose state should be persisted. 
 | 
java.lang.String | 
getName()
Gets the name of the command to display as the action to undo 
 | 
boolean | 
isGeneratePrecedingState()
Determine whether or not the state preceding the invokation of the Command
 should also be generated if a historied Node is found to be dirty. 
 | 
isNeedConfirm, reload, reload, reload, reload, setNeedConfirmenableConfirmation, getAffectedNodes, getContext, getData, getId, getProgressHandle, getType, isGlobal, setContext, setData, setTaskInfo, undopublic java.lang.String getName()
CommandgetName in interface HistoryGeneratingCommandgetName in class Commandpublic int doit()
         throws java.lang.Exception
RevertNodeCommanddoit in class RevertNodeCommandCommand.OK if the reload was successful, otherwise
 Command.CANCELjava.lang.Exceptionpublic Node[] getHistoriedNodes()
HistoryGeneratingCommandgetHistoriedNodes in interface HistoryGeneratingCommandpublic boolean isGeneratePrecedingState()
HistoryGeneratingCommandGenerally speaking, implementations should not have to exercise any conditions; Either a preceding state should always be generated (e.g. a refactoring Command), or never generated (e.g. a Save command). The result of this method will only be considered if a historied Node was first found to be dirty before the invokation of the Command.
Commands of type MULTI_DOCUMENT are always treated as HistoryGeneratingCommands and thus need not implement this interface.
isGeneratePrecedingState in interface HistoryGeneratingCommand