Community
Participate
Working Groups
20051201 I found the following exception in the log, don't know how to reproduce. The stacktrace looks wrong. IMethod.getParameterNames should only throw an exception when the IMethod does not exist. A problem reading the attached Javadoc should be cought in BinaryMethod.getParameterNames and result in the default names 'arg1, arg2....' Java Model Exception: Java Model Status [] at org.eclipse.jdt.internal.core.BinaryMethod.getAttachedJavadoc(BinaryMethod.java:484) at org.eclipse.jdt.internal.core.BinaryMethod.getParameterNames(BinaryMethod.java:202) at org.eclipse.jdt.ui.JavaElementLabels.getMethodLabel(JavaElementLabels.java:500) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:387) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:364) at org.eclipse.jdt.internal.ui.viewsupport.StatusBarUpdater.formatJavaElementMessage(StatusBarUpdater.java:76) at org.eclipse.jdt.internal.ui.viewsupport.StatusBarUpdater.formatMessage(StatusBarUpdater.java:66) at org.eclipse.jdt.internal.ui.viewsupport.StatusBarUpdater.selectionChanged(StatusBarUpdater.java:51) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:785) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761) at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1042) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1062) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:232) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:227) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:393) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3218) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2864) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1763) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1727) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:396) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:106) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:109) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:167) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338) at org.eclipse.core.launcher.Main.basicRun(Main.java:282) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) !SUBENTRY 1 org.eclipse.jdt.core 4 1008 2005-12-01 11:40:15.011 !MESSAGE
Fixed and released in HEAD. No regression test. This error occured because the doc could not be retrieved. It would be interesting to find out why it failed.
Steps in I20051129-1200: - import org.eclipse.ui.ide as binary - open class MarkerAdapter - in the Outline view, select constructor of inner class MarkerCategory The problem could be that the IMethod has two arguments of type MarkerAdapter, but the method declaration has only one.
The problem with the wrong constructor signature is bug 47354.
Verified for 3.2 M4 using build I20051212-0010 (cannot reproduce the exception following comment 2 scenario)
