Bug 84446 OperationHistory should protect itself better against runtime exceptions
Since clients of the history might rely on getting certain events even if a operation causes runtime exceptions (for example listeners) the history should protect itself better agains runtime exceptions. This envloves: - listeners causing runtime exceptions in the call back - Operation execution causing runtime exceptions. In this case listeners must be informed as well.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/DefaultOperationHistory.java
status = getUndoApproval(operation, info);
			if (status.isOK()) {
				status = doUndo(monitor, info, operation, false);
			}
		} else {
			status = OPERATION_INVALID_STATUS;
		}
		return status;
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.core.commands.operations.IOperationHistory#openOperation(org.eclipse.core.commands.operations.IUndoableOperation)
	 */
	public void openOperation(IUndoableOperation operation) {
		if (fBatchingOperation != null) {
			
			
			closeOperation(false, false);	
		} 
		fBatchingOperation = operation;
		notifyAboutToExecute(operation);	
	}
	
	/**
	 * @see org.eclipse.core.commands.operations.IOperationHistory#closeOperation()
	 * @deprecated
	 */
	public void closeOperation() {
		closeOperation(true, true);