OK, it happened again (on a transformation that otherwise was fine), but the error doesn't seem to point to oXygen? This is the stack trace from the first error occurring at the time of my transformation error. I don't expect that anything can be done with this now, but if someone else notices this problem, perhaps we could work together to find out the cause. eclipse.buildId=M20060628-1325 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 This is a continuation of log file C:\eclipse_work\.metadata\.bak_4.log Created Time: 2006-08-16 20:02:11.875 Error Wed Aug 16 20:04:35 CDT 2006 java.lang.NullPointerException java.lang.NullPointerException at org.eclipse.jface.text.hyperlink.HyperlinkManager.deactivate(HyperlinkManager.java:220) at org.eclipse.jface.text.hyperlink.HyperlinkManager.handleEvent(HyperlinkManager.java:448) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:982) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:927) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:965) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:961) at org.eclipse.swt.widgets.Widget.wmKeyUp(Widget.java:1660) at org.eclipse.swt.widgets.Control.WM_KEYUP(Control.java:3571) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3276) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1923) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) On 8/15/06, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
I think it is the standard Eclipse dialog error for runtime exceptions not handled by the current plugin. The content of the Eclipse error log is available in the Error Log view which is an Eclipse built-in view. Open it from Window -> Show View -> Error Log and double click on any line of the table to see details about that error. The last error corresponds to the first line of the table. Please post the details of the transformation error (stack trace, caused by, etc). It is unlikely to receive help to eliminate it before knowing what it is.
Best regards, Sorin
Chris Chiasson wrote:
In transforming a document that came out fine and produced only the standard "stripping ns from DocBook 5/NG ...", "processing stripped ...", "id recommended on..." warnings, the oXygen Eclipse plugin (assumedly) poped up a window saying "an error occurred" and "see error log for details". The dialog had only an OK button. The error doesn't seem to appear on repeats of the same transformation, but I have seen it before when working with the oXygen plugin. I am not sure where to look for the aforementioned log. A search of the oXygen site does not reveal the message. So, to the point:
Has anyone seen this error message? What, if anything, may be done to eliminate it?
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user