Bug 116223 [refactoring] ProcessorBasedRefactoring does not handle exceptions thrown by participants
I20051108-1011 ProcessorBasedRefactoring protects itself against participants that throw an exception in createChange(..). However, it does not catch execptions thrown in initialize(..) or in checkConditions(..). We had a case where initialize(..) threw a ClassCastException, which generated a wrong error message (participant does not extend required type). I think we should protect all call backs and disable participants that throw a RuntimeException.
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/RefactoringCoreMessages.java
public static String ValidateEditChecker_failed;
	
	public static String Changes_validateEdit;
	
	public static String RefactoringCorePlugin_internal_error;
	public static String RefactoringCorePlugin_listener_removed;
	public static String RefactoringCorePlugin_participant_removed;
	
	public static String Resources_outOfSyncResources;
	public static String Resources_outOfSync;
	public static String Resources_modifiedResources;
	public static String Resources_fileModified;
	
	public static String NullChange_name;
	
	public static String TextChanges_error_existing;
	public static String TextChanges_error_not_existing;
	public static String TextChanges_error_content_changed;
	public static String TextChanges_error_unsaved_changes;
	public static String TextChanges_error_read_only;
	public static String TextChanges_error_outOfSync;
	public static String TextChanges_error_document_content_changed;
	
	public static String BufferValidationState_no_character_encoding;
	public static String BufferValidationState_character_encoding_changed;
	
	public static String CheckConditionContext_error_checker_exists;
	public static String CompositeChange_performingChangesTask_name;
	
	public static String ProcessorBasedRefactoring_initial_conditions;