Description Michael Barrett-Lennard 2012-01-09 01:38:36 EST

Build Identifier: org.eclipse.nebula.widgets.tablecombo_1.0.0.201112201439

When running an automated test suite Rational Functional Tester (RFT) against our product we get a NullPointerException which is from inside the TableCombo code. We tried the same steps manually but it works perfectly so this only occurs when being driven from RFT

Here is the stack trace.

SEVERE: An unexpected error occurred: java.lang.NullPointerException
Throwable occurred: java.lang.NullPointerException
	at org.eclipse.nebula.widgets.tablecombo.TableCombo.isDropped(TableCombo.java:1234)
	at org.eclipse.nebula.widgets.tablecombo.TableCombo.access$12(TableCombo.java:1233)
	at org.eclipse.nebula.widgets.tablecombo.TableCombo$5.getName(TableCombo.java:1161)
	at org.eclipse.swt.accessibility.Accessible.get_accName(Accessible.java:2286)
	at org.eclipse.swt.accessibility.Accessible$1.method10(Accessible.java:154)
	at org.eclipse.swt.internal.ole.win32.COMObject.callback10(COMObject.java:155)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at com.ibm.safr.we.ui.Application.start(Application.java:111)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:600)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

Reproducible: Always

Steps to Reproduce:
You will need RFT, our product and our script to reproduce this. Was hoping you could determine something from the stack trace. Here is a copy of the RFT script.

		pushbuttonbutton().click(atPoint(10,7));
		sysListView32table().click(atHeader(atText("ID")));
		// Window: SAFRWE.exe: 
		_32770window().inputKeys("{ExtDown}{ExtDown}{ExtDown}{ExtDown}{ExtDown}{ExtDown}{ExtDown}");
		_32770window().inputKeys("{ExtDown}{ExtDown}{ENTER}");
		
		// Window: SAFRWE.exe: Insert View Source
		pushbuttonbutton2().click(atPoint(5,10));
		
		// Window: SAFRWE.exe: 
		_32770window().inputKeys("{ExtDown}{ENTER}");
		
		// Window: SAFRWE.exe: Insert View Source
		insertViewSourcewindow().inputKeys("{TAB}");
		
		// Window: SAFRWE.exe: Insert View Source
		okbutton().click(atPoint(32,8));

pushbuttonbutton and pushbuttonbutton2 are the down arrow buttons of two table combos in a dialog.