[rzc1]

Hi MyEclipse Team!

We are using ResourceBundle Editor 1.0.6 (see https://github.com/essiembre/eclipse-rbe) for editing resource files.

Since MyEclipse 2017 CI 2 we are seeing the exception below in the logs and the editor cannot open the input windows for the resource texts anymore. It is working with “MyEclipse 2017 CI 1”.

Maybe you have a solution or workaround for this as the Resourcebundle editor is very important for working on resource files.

!ENTRY org.eclipse.ui 4 0 2017-05-03 08:14:59.375
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.SWT.error(SWT.java:4419)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
	at org.eclipse.swt.widgets.Control.getSize(Control.java:1607)
	at org.eclipse.swt.widgets.ScrollBarAdapter.getSize(ScrollBarAdapter.java:57)
	at org.eclipse.swt.custom.ScrolledCompositeLayout.layout(ScrolledCompositeLayout.java:65)
	at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1383)
	at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1794)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4866)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102)
	at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2547)
	at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:88)
	at org.eclipse.swt.widgets.Control.WM_WINDOWPOSCHANGED(Control.java:5691)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4879)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5115)
	at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
	at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1482)
	at org.eclipse.swt.widgets.Control.setBoundsInPixels(Control.java:3251)
	at org.eclipse.swt.widgets.Composite.setBoundsInPixels(Composite.java:1099)
	at org.eclipse.swt.widgets.Control.setBoundsInPixels(Control.java:3212)
	at org.eclipse.swt.widgets.Control.setBoundsInPixels(Control.java:3208)
	at org.eclipse.swt.widgets.Control.setBoundsInPixels(Control.java:3284)
	at org.eclipse.swt.widgets.Control.setBounds(Control.java:3280)
	at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:289)
	at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:91)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1120)
	at org.eclipse.swt.widgets.Sash.WM_LBUTTONUP(Sash.java:334)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4828)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5115)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1492)

Best wishes
Stefan

[support-swapna]

Stefan,

Sorry that you are seeing this issue. MyEclipse 2017 CI is based on Eclipse 4.6.1. I see the exception logged in Eclipse 4.6.1 as well but the file opens in the Resource Bundle editor and I can work with it. In MyEclipse 2017 CI 4, I see the exception logged but could not consistently replicate the issue with the resource files not opening in the editor.

I have filed a bug for the dev team to look into it. If the Resource Bundle editor is very important to you and if the current issue is a showstopper, then you can lock your MyEclipse 2017 to CI 1 and continue working until the fix is out. Go to menu Help > Check for Updates, select MyEclipse 2017 CI 1 and click ‘Lock’. Restart the IDE when it prompts to. We will keep you posted about the fix schedule.

Apologies for inconvenience caused.

–Swapna
MyEclipse Support

[support-swapna]

Stefan,

MyEclipse 2017 CI 5 is out. Please update to CI 5 from Help > Check for Updates and let us know if you are still seeing issues with the ResourceBundle editor.

–Swapna
MyEclipse Support

[rzc1]

Hi Swapna,

just tested MyEclipse 2017 CI 5 and the ResourceBundle Editor is working again 🙂

Thank you for the fast support

Best wishes
Stefan

[support-swapna]

Stefan,

Glad that it works. Thank you for getting back to us.
Please let us know if you see any other issues.

–Swapna
MyEclipse Support

[Author]

Posts