Can't View Database Tables??

Last week for no obvious reason I found I was unable to view database tables in Developer. I get this erro:

Could not open the editor: An unexpected exception was thrown with the log shown below. I figured this might be a corruption in my Servoy install so I made a clean install today - with the same results. I cant figure out from this log where I might target to fix this issue??

I guess from the null pointer the editor is suggesting it can find the Db table, though the solution works and everything else is as expected!

Suggestions welcomed.

The log is as follows:

java.lang.NullPointerException
	at com.servoy.eclipse.ui.editors.table.EventsComposite.initDataBindings(EventsComposite.java:152)
	at com.servoy.eclipse.ui.editors.table.EventsComposite.<init>(EventsComposite.java:95)
	at com.servoy.eclipse.ui.editors.TableEditor.createEventsPage(TableEditor.java:335)
	at com.servoy.eclipse.ui.editors.TableEditor.createPages(TableEditor.java:130)
	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:357)
	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662)
	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:286)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2857)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762)
	at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
	at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
	at com.servoy.eclipse.ui.util.EditorUtil.openTableEditor(EditorUtil.java:197)
	at com.servoy.eclipse.ui.views.solutionexplorer.actions.OpenTableAction.run(OpenTableAction.java:71)
	at com.servoy.eclipse.ui.views.solutionexplorer.actions.ContextAction.run(ContextAction.java:115)
	at com.servoy.eclipse.ui.views.solutionexplorer.SolutionExplorerView$10.doubleClick(SolutionExplorerView.java:1169)
	at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.runtime.Platform.run(Platform.java:888)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
	at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:819)
	at org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1083)
	at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195)
	at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238)
	at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
	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:368)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

don’t you have any reading errors in front of that?
it kind of looks that one module is not really loading (but the project does exists)

jcompagner:
don’t you have any reading errors in front of that?
it kind of looks that one module is not really loading (but the project does exists)

Don’t know what errors in front of it means but I don’t get any other errors at all and it only occurs when I look at a table through explorer>servers>tables.

All of the modules are fine - no problems reported either?

if you edit the moduleNames property of the main solution (you remove and add a module) and save that
does that help? It really seems to be a module that is not completely correct.

to be sure: don’t you really not have any other errors in the log file?

jcompagner:
if you edit the moduleNames property of the main solution (you remove and add a module) and save that
does that help? It really seems to be a module that is not completely correct.

to be sure: don’t you really not have any other errors in the log file?

No Johan removing and saving modules does not make a difference?

if i look at the code, at that place there can’t really be a null pointer, it can but only if there is really a problem with 1 of the modules of one of the modules/solution

So i guess if you don’t have any other error in the log files i would have to have a look in your workspace itself.

jcompagner:
if i look at the code, at that place there can’t really be a null pointer, it can but only if there is really a problem with 1 of the modules of one of the modules/solution

So i guess if you don’t have any other error in the log files i would have to have a look in your workspace itself.

New workspace and a full download from svn fixed it - bit worrying though!

Thanks for the GuruNess Johan.

Ian