Controlling how error handlers for specific elements are displayed

The following code is an example for the Details section of the Advanced page in the test editor. In the layoutControls method, add code similar to these lines:

m_exceptionUi = new TestExceptionProducerUI( 
	getTestEditor(),
	new AuthenticationExceptionCreator());
m_exceptionUi.createErrorProducerContents( 
	getDetails(), 
	getNtlm(),
	(LoadTestWidgetFactory) getFactory());

The AuthenticationExceptionCreator class is the same class that is specified in the plugin.xml file in the exceptionDefinition extension point. In the refreshControls method, add code similar to this line:

m_exceptionUi.refresh( getNtlm() );

The following code is an example for dialog boxes and properties pages. In the createContents method or the createDialogArea method, add code similar to these lines:

m_errorHandling = new DialogExceptionProducerUI(
	m_page.getEditor(),
	new PageTitleErrorExceptionCreator());
m_errorHandling.createErrorProducerContents( parent, vp );

In the onCancelPressed method, which is called when the user clicks Cancel in a dialog box, add code similar to this line:

m_errorHandling.cleanUp();

When the user clicks OK in a dialog box or property page, the changes are applied to the CBError object immediately, so no extra code is required. When the user clicks Cancel in a dialog box or property page, the changes must be undone using the cleanUp method.

To receive notifications when changes are made to a CBError object, override the updateEditor method by using this code:

m_errorHandling = new DialogExceptionProducerUI( 
			TestEditorPlugin.getEditorFor(m_datapool), 
			new EndOfDatapoolExceptionCreator()){
		@Override
		protected void updateEditor() {
			getButton(OK).setEnabled(true);
			super.updateEditor();
		}
	};
	m_errorHandling.createErrorProducerContents(composite, m_datapool, null );