[Robert Byrne]

I was doing a “paste” into my jsp file when I received an error saying that the paste did not finish properly. I looked through the file as I had red error lines everywhere and saw that a line, which had nothing to do with the paste and located 20 lines up the file from the pasted section, was chopped in half and half was missing from the immediate area.

I then tried “undo” last command, which threw another error. Something about not being able to execute the undo. I’m sorry I do not have these details for you.

I proceeded to close the file and reopen it. It would not open and I received the error below. But then I tried closing the entire IDE and reopening it. Still, the error below.

The “paste” and “undo” commands I run from the keyboard, “CTRL-v” and “CTRL-z”. I was pasting a style color, six characters long.

I am running on XP, sp2.
I am using Resin 3.1.3 in case that’s an issue, and it was running through eclipse at the time as I was testing html styles.

Matisse Swing UI Designer MyEclipse
Version: 6.0.1.zmyeclipse601200710
Build id: 6.0.1-GA-200710

ICEfaces AJAX and Java EE Tooling for MyEclipse
Version: 6.0.1.zmyeclipse601200710
Build id: 6.0.1-GA-200710

Eclipse Data Tools Platform Connectivity Open Data Access (ODA) Designer
Version: 1.5.1.200709261
Build id: 1.0.0.200611131

Dali Java Persistence API (JPA) Tools
Version: 0.5.0.zmyeclipse601200710
Build id: @build@

Eclipse Modeling Framework (EMF)
Version: 2.3.1.v200709252135
Build id: 200709252135

The error stack:
java.lang.RuntimeException: DOMCoordinator#createDesignNodeFromSource: Node type DOCUMENT_TYPE_NODEnot supported.
at com.genuitec.eclipse.webdesigner3.DOMCoordinator.createDesignNodeFromSource(DOMCoordinator.java:563)
at com.genuitec.eclipse.webdesigner3.DOMCoordinator.buildDesignDOMChildren(DOMCoordinator.java:437)
at com.genuitec.eclipse.webdesigner3.DOMCoordinator.rebuildDesignNodesFromSource(DOMCoordinator.java:1746)
at com.genuitec.eclipse.webdesigner3.design.DesignEditSystem.synchronize(DesignEditSystem.java:185)
at com.genuitec.eclipse.webdesigner3.AbstractEditSystem.setSynchronized(AbstractEditSystem.java:24)
at com.genuitec.eclipse.webdesigner3.WebDesigner3.setSynchronized(WebDesigner3.java:113)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.checkSynchronization(WebDesignerMultiPageEditor.java:936)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.access$6(WebDesignerMultiPageEditor.java:932)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor$10.run(WebDesignerMultiPageEditor.java:909)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.designPageChange(WebDesignerMultiPageEditor.java:907)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.pageChange(WebDesignerMultiPageEditor.java:881)
at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:697)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:287)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2565)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:286)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:857)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
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.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
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(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
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(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)

[Loyal Water]

Your file seems to have got corrupted. Can you switch to a new workspace, create a new proejct and try opening your JSP file. Does it work ?

[Sapan Vora]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Sapan Vora]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[manncrk]

Have seen questions on this type of error posted, but no resolution. Might help reduce time/effort spent by others if a resolution gets posted…

MyEclipse 6.0.1 (full download, 6.0.1-GA-200710), XP sp2, Java 1.6.0_01.

This morning rec’d error: “DOMCoordinator#createDesignNodeFromSource: Node type DOCUMENT_TYPE_NODEnot supported” when I tried to re-open an HTML file with the 6.0.1 Visual HTML Design editor (had edited / exported this file to a server site several times with 6.0.1 on previous days). [Previous to my downloading and using 6.0.1 last weekend, workspace/files were created under 5.1.1.] After searching this site for any hints, tried the following things to try to define the issue:

(1) Opened copy of subject workspace with 5.1.1 — successfully opened Visual editor on subject HTML file, in both “design” and “preview” panes.
(2) Tried to open previous copy (from CVS) of subject HTML file with 6.0.1 (file was edited and exported earlier with 6.0.1) — rec’d “DOMCoordinator…” error.
(3) Opened workspace created several weeks ago (with 5.1.1) with 6.0.1 and tried to open subject HTML file in Visual Designer — rec’d “DOMCoordinator…” error.
(4) Uninstalled 6.0.1 (hung in “Registry…Uninstalling HKEY_CLASSES_ROOT\Applications\xmleditor.exe\Su…”) — terminated uninstall after time, rebooted, deleted old 6.0.1 install directory.
(5) Re-downloaded / reinstalled full 6.0.1. Opened (a) original and (b) copy of original workspace, tried to access subject HTML — both times rec’d “DOMCoordinator…” error.
(6) Tried to access other HTML files in original workspace with 6.0.1; all HTML files in WebRoot directory opened properly (“design” and “preview” panes) in Visual editor. HTML files in WebRoot sub-directories either (a) opened properly in “design” pane but an Information dialog “This program cannot display the webpage…Most likely causes:…” displayed in “preview” pane or (b) rec’d “DOMCoordinator…” error. The HTML files that created (a) are just wrappers around a forwarding to .jpg files (see ** below). The HTML files that create (b) all contain imbedded refs to .jpg files (<img src=—.jpg>). The HTML files in WebRoot (that don’t cause errors) also contain imbedded .jpg references (<img src=—.jpg>).
(7) Again tried 5.1.1 on original workspace and subject HTML file — successfully opened Visual editor on subject HTML file (and sub-directory HTML files), in both “design” and “preview” panes.
(8) “Un-did” working set in which this project appeared (i.e. went back to displaying all projects together) and exited 5.1.1. Opened working set with 6.0.1 and again tried opening HTML files — see (6).

**One time only, I received an Information dialog box that indicated “?Visual Designer?” was looking in “‘myworkspace’/.metadata/.plugins/com.genuitec.eclipse.webdesigner3″ for a .jpg that the wrapping HTML file was forwarding to (<meta http-equiv=”Refresh” content=”0; URL=griffith3.jpg”/>).

I’d appreciate any thoughts…

Fallback is to return to 5.1.1 where this all works…

Regards,
Bob

[Loyal Water]

Hi Bob,
Thank you for taking time out to post your findings. We appreciate your help.

[Sapan Vora]

Was there any resolution for this bug? I can sort of workaround it, by opening the jps file in something other than the designer mode, but whe I debug that jsp, it tries to open it in the visual designer mode, and the page won’t open. Is there a way to work around that (with MyEclipse 6.0)?? Until a fix is posted.

Thanks.

[manncrk]

A resolution of this issue has been promised for some time. What’s up?

[Loyal Water]

manncrk,
Im afraid the team is still working on this issue. Hopefully the fix would come in the 6.5 GA release.

[Sapan Vora]

*** Date:
Saturday, July 19, 2008 12:48:57 AM PDT

** System properties:
OS=WindowsVista
OS version=6.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.0 GA
Build id: 6.5.0-GA-20080609

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.5.0 GA
Build id: 6.5.0-GA-20080609

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\userx\AppData\Local\MyEclipse 6.5\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Users\userx\AppData\Local\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Users\userx\AppData\Local\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
12b8_64
-clean
-vm
C:\Users\userx\AppData\Local\MyEclipse 6.5\jre\bin\javaw.exe

Looks like this bug is still not fixed

DOMCoordinator#createDesignNodeFromSource: Nody type DOCUMENT_TYPE_NODEnot supported.

[scr1701]

Not sure if this will help the original poster – but I had the same error: “Node type DOCUMENT_TYPE_NODEnot supported”, and I had the following code:

…
<%@ taglib uri=”http://java.sun.com/jstl/fmt&#8221; prefix=”fmt”%>
<fmt:bundle basename=”com.mycompany.struts.ApplicationResources”>
…
<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>
<html:html lang=”true”>
<head>
<html:base />

<title><fmt:message key=”UserRoleGroups.title”/></title>
…

I moved the

<fmt:bundle basename=”com.mycompany.struts.ApplicationResources”>

after the DOC-TYPE declaration, and that seemed to solve my problem! Hope that helps someone.

[Loyal Water]

scr1701,
Thank you for posting this information. I’m sure it would be helpful to the users on this forum.

[Author]

Posts