Could Not Open the Editor error
Using standard 2.0.0.1 server, with a 2.0 client, I am receiving an error message of "Could not open the editor: An unexpected exception was thrown" which is preventing me from creating (and/or saving and then opening) artifacts in my RRC Project. I can seemingly create most artifacts fine. For example, I have no issues sketching a user interface...but when I save and then attempt to open that artifact, I get this error. It seems to be consistent across all types of RRC artifacts (use cases, use case diagrams, storyboards, et al). Any help would be much appreciated.
I will add that i found one similar instance/post here of this happening. That individual said that they tried to archive the default project using the web admin UI and then created a new project using the rich client. Upon attempting this, I select to create a Project using the default folders and attributes and upon selecting Finish, cannot proceed. This screen simply reappears upon selecting Finish: Thanks-John Here are the associated details: java.lang.NullPointerException at com.ibm.rdm.integration.calm.ui.actions.CreateCalmLinkAction.isEnabled(CreateCalmLinkAction.java:81) at com.ibm.rdm.integration.calm.ui.AbstractCalmLinkSidebarSectionProvider.isVisible(AbstractCalmLinkSidebarSectionProvider.java:56) at com.ibm.rdm.linking.ui.LinksSidebarComposite.createCreateActions(LinksSidebarComposite.java:828) at com.ibm.rdm.linking.ui.LinksSidebarComposite.fillToolBar(LinksSidebarComposite.java:701) at com.ibm.rdm.ui.widget.SidebarContentComposite.create(SidebarContentComposite.java:275) at com.ibm.rdm.ui.widget.SidebarContentComposite.<init>(SidebarContentComposite.java:106) at com.ibm.rdm.linking.ui.LinksSidebarComposite.<init>(LinksSidebarComposite.java:560) at com.ibm.rdm.linking.ui.LinksSidebarSection.createContent(LinksSidebarSection.java:52) at com.ibm.rdm.platform.ui.sidebar.SidebarSection.createPartControl(SidebarSection.java:74) at com.ibm.rdm.platform.ui.sidebar.SidebarContext.createPartControl(SidebarContext.java:39) at com.ibm.rdm.platform.ui.sidebar.FlyoutSidebarComposite$ContextSidebarProvider.createSidebar(FlyoutSidebarComposite.java:68) at com.ibm.rdm.gef.InternalFlyoutSidebarComposite.setState(InternalFlyoutSidebarComposite.java:567) at com.ibm.rdm.platform.ui.sidebar.FlyoutSidebarComposite.setState(FlyoutSidebarComposite.java:48) at com.ibm.rdm.gef.InternalFlyoutSidebarComposite.updateState(InternalFlyoutSidebarComposite.java:618) at com.ibm.rdm.platform.ui.sidebar.FlyoutSidebarComposite.applyStatePreference(FlyoutSidebarComposite.java:59) at com.ibm.rdm.ba.ui.diagram.editors.BAGraphicalEditor.doCreatePartControl(BAGraphicalEditor.java:592) at com.ibm.rdm.ba.ui.diagram.editors.BaseDiagramEditor.doCreatePartControl(BaseDiagramEditor.java:785) at com.ibm.rdm.ba.ui.diagram.editors.BAGraphicalEditor.createPartControl(BAGraphicalEditor.java:721) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at com.ibm.rdm.ui.utils.DocumentUtil.openEditor(DocumentUtil.java:323) at com.ibm.rdm.ui.server.editor.input.RepositoryEditorInputHelper.openEditorFor(RepositoryEditorInputHelper.java:63) at com.ibm.rdm.ui.gef.editor.input.EditorInputHelper.openEditor(EditorInputHelper.java:37) at com.ibm.rdm.ui.gef.editor.input.EditorInputHelper.openEditor(EditorInputHelper.java:29) at com.ibm.rdm.ui.gef.editor.input.EditorInputHelper.openEditor(EditorInputHelper.java:25) at com.ibm.rdm.ui.search.figures.ResourceNameFigure$NavigateLinkActionHandler.handleAction(ResourceNameFigure.java:52) at com.ibm.rdm.ui.search.figures.ResourceNameFigure$6.run(ResourceNameFigure.java:171) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.ibm.rdm.ui.search.figures.ResourceNameFigure.navigateLink(ResourceNameFigure.java:169) at com.ibm.rdm.ui.search.figures.ResourceNameFigure$5.actionPerformed(ResourceNameFigure.java:156) at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:200) at org.eclipse.draw2d.Clickable.doClick(Clickable.java:186) at com.ibm.rdm.ui.search.figures.ResourceNameFigure$4.handleStateChanged(ResourceNameFigure.java:145) at org.eclipse.draw2d.Clickable.fireStateChanged(Clickable.java:215) at org.eclipse.draw2d.Clickable$1.handleStateChanged(Clickable.java:175) at org.eclipse.draw2d.ButtonModel.fireStateChanged(ButtonModel.java:199) at org.eclipse.draw2d.ButtonModel.setArmed(ButtonModel.java:347) at com.ibm.rdm.ui.search.figures.ResourceNameFigure$2.mouseReleased(ResourceNameFigure.java:117) at org.eclipse.draw2d.Figure.handleMouseReleased(Figure.java:883) at org.eclipse.draw2d.SWTEventDispatcher.dispatchMouseReleased(SWTEventDispatcher.java:239) at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:368) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:538) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:207) 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:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.ibm.rdm.ui.application.ReqComposerApplication.start(ReqComposerApplication.java:122) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:386) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) |
3 answers
While it should be fine to use a 2.0 client with a 2.0.0.1 server, is there a reason you have not updated the client? Obviously there have been a lot of bug fixes, so if you've updated the server anyway, it might be good to update the client as well to see if it resolves your problem.
In the meantime, you might first verify that the user you are connecting with has appropriate repository permissions AND client license (ie, do you have the Author license?). |
Yes, I actually recognized that this might be the case and just finished updating the client to 2.0.0.1 a few minutes ago. It seems to work perfectly. So for anyone who may encounter a similar scenario...it seems advisable to use the 2.0.0.1 client with the 2.0.0.1 server.
Thanks Stef. |
Again, I don't necessarily think it was the mismatch causing the problem (though it could, but it's supposed to work) because it could have just as easily been something we fixed in the 2.0.0.1 client that you were hitting.
As for when 2.0.0.2 comes out, that really will require matching the client and server due to the nature of some of the fixes going in that release. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.