Bug 88352 Operation supports leaks contexts via action handler
I20050315-1100 Susan, this is a different leak from the one that I reported. Test Case: 1. open text editor 2. close text editor ==> DefaultUndoManager is leaked due to undo/redo actions handlers still holding on to the context.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/IOperationHistory.java
* @return the IStatus indicating whether the redo succeeded.
	 * 
	 * The severity code in the returned status describes whether the operation
	 * succeeded and whether it remains in the history. <code>OK</code>
	 * severity indicates that the redo operation was successful and that the
	 * operation has been placed on the undo history. Listeners will receive the
	 * <code>REDONE</code> notification.
	 * 
	 * <code>CANCEL</code> severity indicates that the user cancelled the
	 * operation and that the operation remains in the redo history.
	 * <code>ERROR</code> severity indicates that the operation could not
	 * successfully be redone and that it has been removed from the history.
	 * Listeners will also be notified that the operation was removed. Any other
	 * severity code is not specifically interpreted by the history, and is
	 * simply passed back to the caller. For all severities other than
	 * <code>OK</code>, listeners will receive the
	 * <code>OPERATION_NOT_OK</code> notification instead of the
	 * <code>REDONE</code> notification.
	 * 
	 * @throws ExecutionException
	 *             if an exception occurred during redo.
	 * 
	 */
	IStatus redo(IUndoContext context, IProgressMonitor monitor, IAdaptable info)
			throws ExecutionException;
	/**
	 * Redo the specified operation
	 * 
	 * @param operation -
	 *            the operation to be redone