Question

在过去的几天里，我的Domino Designer（9.0.1）一直在“忘记”我的Applications Eclipse View中显示的应用程序。它最初是零星的，所以不是每天都有，而且认为这是一次性的临时性事情。现在它正在抛出一个有趣的错误。

screen shot of my error in DDE

我还应该补充一点，在一位同事的建议之后，我重命名了我的工作区文件夹，这使我能够从头开始重新构建它，并且它又回到了工作状态。因此，为了确定这一点，它不再是一个直接的危机（这将阻止我使用Designer与nsf进行交互），它更像是：

好奇心，而不是显示塞子
训练时刻，所以我可以了解到这一切是什么意思
希望，我的一些学识渊博的开发人员可以在故障排除和阅读此错误方面留下一些优秀的技能（因为我看到的是一个空指针异常，与我的com.ibm.designer.domino.navigator.DDViewer相关和我的org.eclipse.ui.internal.Workbench *）

任何输入都将不胜感激。如果我能够更好地确定自己的故障排除工作，我会将这个问题视为“已回答”;为了消除如此严厉的方法来“修复”我的设计师环境，应该再次出现。

图片中的错误全文：

java.lang.NullPointerException
        at com.ibm.icu.text.RuleBasedCollator.getFirstUnmatchedOffset(Unknown Source)
        at com.ibm.icu.text.RuleBasedCollator.compare(Unknown Source)
        at com.ibm.designer.domino.navigator.DesignerNavResourceComparator.compare(Unknown Source)
        at org.eclipse.jface.viewers.ViewerComparator$1.compare(Unknown Source)
        at java.util.Arrays.mergeSort(Unknown Source)
        at java.util.Arrays.sort(Unknown Source)
        at java.util.Arrays.sort(Unknown Source)
        at org.eclipse.jface.viewers.ViewerComparator.sort(Unknown Source)
        at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(Unknown Source)
        at com.ibm.designer.domino.navigator.DDViewer.getChildren(Unknown Source)
        at com.ibm.designer.domino.navigator.DDViewer.internalRefresh(Unknown Source)
        at com.ibm.designer.domino.navigator.DDViewer.inputChanged(Unknown Source)
        at org.eclipse.jface.viewers.ContentViewer.setInput(Unknown Source)
        at org.eclipse.jface.viewers.StructuredViewer.setInput(Unknown Source)
        at com.ibm.designer.domino.navigator.DDNavigator.refreshContents(Unknown Source)
        at com.ibm.designer.domino.navigator.DDNavigator.createPartControl(Unknown Source)
        at org.eclipse.ui.internal.ViewReference.createPartHelper(Unknown Source)
        at org.eclipse.ui.internal.ViewReference.createPart(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchPartReference.getPart(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchPage$17.runWithException(Unknown Source)
        at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(Unknown Source)
        at org.eclipse.swt.widgets.Synchronizer.syncExec(Unknown Source)
        at org.eclipse.ui.internal.UISynchronizer.syncExec(Unknown Source)
        at org.eclipse.swt.widgets.Display.syncExec(Unknown Source)
        at org.eclipse.ui.internal.StartupThreading.runWithoutExceptions(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchPage.restoreState(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchWindow.restoreState(Unknown Source)
        at com.ibm.rcp.personality.framework.internal.PersonalityWindowStateStore.restoreState(Unknown Source)
        at com.ibm.rcp.platform.personality.DefaultWorkbenchWindowAdvisor.postWindowCreate(Unknown Source)
        at com.ibm.designer.domino.rcp.personality.DesignerWorkbenchWindowAdvisor.postWindowCreate(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchWindow.fireWindowCreated(Unknown Source)
        at org.eclipse.ui.internal.WorkbenchWindow.open(Unknown Source)
        at org.eclipse.ui.internal.Workbench$22.runWithException(Unknown Source)
        at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(Unknown Source)
        at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
        at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Unknown Source)
        at com.ibm.rcp.personality.framework.internal.RCPWorkbenchAdvisor.openWindows(Unknown Source)
        at org.eclipse.ui.internal.Workbench$27.runWithException(Unknown Source)
        at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(Unknown Source)
        at org.eclipse.swt.widgets.Synchronizer.syncExec(Unknown Source)
        at org.eclipse.ui.internal.UISynchronizer.syncExec(Unknown Source)
        at org.eclipse.swt.widgets.Display.syncExec(Unknown Source)
        at org.eclipse.ui.internal.StartupThreading.runWithoutExceptions(Unknown Source)
        at org.eclipse.ui.internal.Workbench.init(Unknown Source)
        at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
        at org.eclipse.ui.internal.Workbench.access$4(Unknown Source)
        at org.eclipse.ui.internal.Workbench$5.run(Unknown Source)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
        at com.ibm.rcp.personality.framework.internal.RCPApplication.run(Unknown Source)
        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.internal.app.EclipseAppContainer.callMethodWithException(Unknown Source)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        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(Unknown Source)
        at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
        at org.eclipse.equinox.launcher.Main.run(Unknown Source)
        at com.ibm.rcp.core.internal.launcher.Main.startLaunch(Unknown Source)
        at com.ibm.rcp.core.internal.launcher.Main.main(Unknown Source)
        at com.ibm.rcp.core.internal.launcher.Main.run(Unknown Source)

Answer 1

此问题已作为SPR TMDS97PURR报告给IBM开发人员。在那种情况下，开发人员设计器客户端已经崩溃，然后以您提到的方式失败。

他们删除了他们的工作区并继续进行。开发人员无法重现该问题，因此无法重现。

如果您能够打开PMR，您可以将破碎的工作区提交给SPR，如果您希望他们进一步调查的话。

Answer 2

我找到的修复程序涉及编辑Data \ workspace.metadata.plugins \ com.ibm.designer.domino.ide.resources \ wsInfo.xml

在我的情况下，该文件看起来状态良好但是对于最后几个＆＃39;项目＆＃39;条目。通常情况下，他们缺少另一个项目＆＃39;条目具有＆＃39; replicaid＆＃39;或＆＃39; servername＆＃39;

删除这些行成功启用Designer，而不会丢失所有工作集。

当一个人支持超过20个依赖数据库的20多个应用程序模板时，丢失所有工作集是一件巨大的痛苦。

因此，请尝试从wsInfo.xml中删除一些违规行并享受固定的Designer。

IBM：请随意解析wsInfo.xml更强大，这样就不再发生了。

如何解决/修复Domino Designer中的应用程序清空问题？

2 个答案: