| 
| Assertin failed for editor. [message #327691] | Tue, 29 April 2008 02:09  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: automatic.javalobby.org 
 Hi,
 
 I am getting the AssertionFailed error given below, when trying to edit a column in tableViewer. I extended EditingSupport and in the getCellEditor return ComboBoxEditor for boolean values and TextEditor for the rest of the data. Similar to the editor snipet given below.
 http://wiki.eclipse.org/index.php/JFaceSnippets#Snippet034Ce llEditorPerRowNewAPI
 
 Could anyone help me why the error occurs or let me know if you need more details.
 
 org.eclipse.core.runtime.AssertionFailedException: assertion failed:
 at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
 at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95)
 at  org.eclipse.jface.viewers.ComboBoxCellEditor.doSetValue(Comb oBoxCellEditor.java:220)
 at  org.eclipse.jface.viewers.CellEditor.setValue(CellEditor.jav a:825)
 at  org.eclipse.jface.viewers.EditingSupport.initializeCellEdito rValue(EditingSupport.java:96)
 at  org.eclipse.jface.viewers.ColumnViewerEditor.activateCellEdi tor(ColumnViewerEditor.java:168)
 at  org.eclipse.jface.viewers.ColumnViewerEditor.handleEditorAct ivationEvent(ColumnViewerEditor.java:367)
 at  org.eclipse.jface.viewers.ColumnViewer.triggerEditorActivati onEvent(ColumnViewer.java:621)
 at  org.eclipse.jface.viewers.ColumnViewer.handleMouseDown(Colum nViewer.java:605)
 at  org.eclipse.jface.viewers.ColumnViewer.access$0(ColumnViewer .java:601)
 at  org.eclipse.jface.viewers.ColumnViewer$1.mouseDown(ColumnVie wer.java:107)
 at  org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:178)
 at  org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
 at  org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3673)
 at  org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3284)
 at  org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2365)
 at  org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2329)
 at  org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 04)
 at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
 at  org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
 at  org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)
 at  org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
 at  org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:106)
 at  org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:153)
 at  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:106)
 at  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:76)
 at  org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
 at  org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
 at  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at  org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 497)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1137)
 
 Thank You in advance,
 dheer
 |  |  |  | 
|  | 
|  | 
| 
| Re: Assertin failed for editor. [message #327749 is a reply to message #327743] | Wed, 30 April 2008 08:02  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: merks.ca.ibm.com 
 dheer,
 
 I kind of figured that was the case, since I had the same problem many
 moons ago.  But you know what they say about giving a guy a fish verses
 teaching him how to fish. This is why I often describe the debugger as
 your best friend; it answers questions faster than any newsgroup ever
 well.  Note that if you run your runtime workspace with the -consolelog
 argument, the stack traces will be printed to the console and Eclipse
 lets you click on a stack frame to navigate to the source, so that's a
 very hand thing as well.  Best of luck with your Eclipse adventures...
 
 
 reindheer wrote:
 > Hi Ed,
 >
 > Thank you for the suggestion. I could have avoided this posting if i had not been lazy enough to debug the source.
 >
 > it takes a integer value for ComboBoxCellEditor, whereas i pass on a string.
 >
 > Thank You,
 > dheer
 >
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.03195 seconds