Community
Participate
Working Groups
Created attachment 181913 [details] XML file that VEX can't open Version 0.5.0.201008261158 !ENTRY org.eclipse.wst.xml.vex.ui 4 0 2010-10-28 09:54:59.632 !MESSAGE Unexpected error opening simple.jrctx. Please report a bug to the component wtp.inc.vex at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=WTP%20Incubator !STACK 0 java.lang.NullPointerException at org.eclipse.wst.xml.vex.core.internal.dom.DOMDocumentReader.read(DOMDocumentReader.java:39) at org.eclipse.wst.xml.vex.ui.internal.editor.VexEditor.loadInput(VexEditor.java:347) at org.eclipse.wst.xml.vex.ui.internal.editor.VexEditor.createPartControl(VexEditor.java:483) 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.actions.OpenWithMenu.openEditor(OpenWithMenu.java:344) at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) 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(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
(In reply to comment #0) Do you have a plug-in installed or in your workspace which provides the DTD? (see http://wiki.eclipse.org/Vex/UserGuide#Vex_Plug-in_Project:_Configure_your_own_XML_format) Vex can only open files if their DTD is configured, either by an installed plug-in that extends the extension point 'org.eclipse.wst.xml.vex.ui.doctypes', or by a Vex plug-in project in your workspace. The plug-ins 'org.eclipse.wst.xml.vex.dita' and 'org.eclipse.wst.xml.vex.doctbook' are examples for plug-ins that provide the configuration for a document type.
I guess I don't have any plugin for this file type and don't have time to write one. It told me to file a bug report so that's what I did. It seems like a less than helpful way for VEX to fail.
If a document is opened in Vex that has no document type declared or uses an unknown document type, Vex should display a special error message which describes this problem and gives a hint on possible solutions to the underlying problem: 1. add a doctype declaration to the document 2. configure the document type e.g. by creating a Vex Plug-in in your workspace
Moved to Mylyn Docs Vex.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
