Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » FileDialog broken in Kepler ?
FileDialog broken in Kepler ? [message #1066633] Wed, 03 July 2013 10:04 Go to next message
Cedric Moonen is currently offline Cedric Moonen
Messages: 269
Registered: August 2009
Senior Member
Hello,

I just upgraded my RCP application from Indigo to Kepler. I has an issue with FileDialog: when the open method is called, the FileDialog does not appear and my application hangs.

I use it in the simplest way possible:

FileDialog fileDialog = new FileDialog(getShell());
String filePath = fileDialog.open();


Any idea what the problem could be ?

Thanks.
Re: FileDialog broken in Kepler ? [message #1066641 is a reply to message #1066633] Wed, 03 July 2013 10:23 Go to previous message
Cedric Moonen is currently offline Cedric Moonen
Messages: 269
Registered: August 2009
Senior Member
This is in fact linked to another problem that I have (the FileDialog works fine in another situation).

After the upgrade to Kepler, I kept getting the following exception:

org.osgi.framework.BundleException: Could not find bundle: org.eclipse.equinox.console
	at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:211)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298)
	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.equinox.launcher.Main.invokeFramework(Main.java:636)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1426)


(The exception was thrown because I have the -console argument passed to my application).

So, I added this plugin to my launch configuration (with the required plugins). When I did that, the exception was not thrown anymore and the OSGi console was displayed in the Eclipse console, but my application didn't start. I had to type "ss" in the OSGi console and then the application was started properly.

If I remove this console plugin from my launch configuration, the FileDialog works fine, so I guess that the reason why it was hanging was because a plugin was not properly started (because of the console interfering ?)

[Updated on: Wed, 03 July 2013 10:25]

Report message to a moderator

Previous Topic:MainMenu isn't persisted
Next Topic:Showing properties of e4 view selection in 3.x Properties view
Goto Forum:
  


Current Time: Fri Aug 01 20:34:04 EDT 2014

Powered by FUDForum. Page generated in 0.09974 seconds