Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Legacy RCP Applications
Legacy RCP Applications [message #444688] Fri, 31 July 2009 17:57 Go to next message
Chris is currently offline ChrisFriend
Messages: 97
Registered: July 2009
Member
It's my understanding that the latest stable build of Eclipse e4 0.9 RC2
should be able to launch legacy RCP applications, but I am not having very
much success. If this is the wrong forum for this discussion, can you
point me to the correct one?

For my first attempt, I tried creating a simple RCP application using
Eclipse 3.5 and the provided template "RCP Application with a view". I
opened up the MANIFEST.MF and I launched my simple RCP application
successfully using the link under "Testing" called "Launch and Eclipse
application".

I then ran Eclipse e4 v0.9 RC2 and created a new workspace and imported
that plugin. When I tried to launch the RCP application using e4, I
received a BundleException that said the Activator is invalid and the root
cause of that exception was a ClassNotFoundException stating it could not
find the Activator.

I checked the /bin directory, everything is there as it should be. It
just seems like it expects the class files to be somewhere else. Are
there any gotchas that I should be aware of when running a legacy RCP
application like the one created using the template?

Thanks,
Chris
Re: Legacy RCP Applications [message #453011 is a reply to message #444688] Sat, 01 August 2009 14:47 Go to previous messageGo to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

It's probably not that. Usually if it can't find the activator, that means something else prevented the activator from starting. Sometimes a runtime exception in the start(BundleContext) method, for example.

When running in E4 (and the GA version is available, it contains some important fixes over RC2) you would need to make sure you include the appropriate fragments and all of the e4 plugins that support the modelled workbench. For example:

org.eclipse.e4.ui.workbench.fragment
org.eclipse.e4.ui.workbench.renderers.swt
org.eclipse.e4.ui.workbench.renderers.swt.contributions
org.eclipse.e4.ui.workbench
etc


PW


Re: Legacy RCP Applications [message #468205 is a reply to message #453011] Tue, 04 August 2009 14:06 Go to previous message
Chris is currently offline ChrisFriend
Messages: 97
Registered: July 2009
Member
Adding those e4 plugins helped get rid of the Activator invalid exception,
thanks. The only plugin I didn't see listed as an available plugin to add
as a dependency was the org.eclipse.e4.ui.workbench.fragment, I see it in
the plugin folder of the e4 installation, but only the "source" version
was visible in the plug-in selection dialog. I'm not sure if that had
anything to do with my new issue.

The new problem I have run into is that in my ApplicationWorkbenchAdvisor
class, createWorkbenchWindowAdvisor(...) never gets called with a
configurer. In the Application class start method, the return code is 2.
Any ideas on what would cause the createWorkbenchWindowAdvisor not to be
called?

I am calling PlatformUI.createAndRunWorkbench(display, new
ApplicationWorkbenchWindowAdvisor())

Thanks,
Chris
Re: Legacy RCP Applications [message #561882 is a reply to message #444688] Sat, 01 August 2009 14:47 Go to previous message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

It's probably not that. Usually if it can't find the activator, that means something else prevented the activator from starting. Sometimes a runtime exception in the start(BundleContext) method, for example.

When running in E4 (and the GA version is available, it contains some important fixes over RC2) you would need to make sure you include the appropriate fragments and all of the e4 plugins that support the modelled workbench. For example:

org.eclipse.e4.ui.workbench.fragment
org.eclipse.e4.ui.workbench.renderers.swt
org.eclipse.e4.ui.workbench.renderers.swt.contributions
org.eclipse.e4.ui.workbench
etc


PW


Re: Legacy RCP Applications [message #561945 is a reply to message #453011] Tue, 04 August 2009 14:06 Go to previous message
Chris  is currently offline Chris Friend
Messages: 4
Registered: September 2009
Junior Member
Adding those e4 plugins helped get rid of the Activator invalid exception,
thanks. The only plugin I didn't see listed as an available plugin to add
as a dependency was the org.eclipse.e4.ui.workbench.fragment, I see it in
the plugin folder of the e4 installation, but only the "source" version
was visible in the plug-in selection dialog. I'm not sure if that had
anything to do with my new issue.

The new problem I have run into is that in my ApplicationWorkbenchAdvisor
class, createWorkbenchWindowAdvisor(...) never gets called with a
configurer. In the Application class start method, the return code is 2.
Any ideas on what would cause the createWorkbenchWindowAdvisor not to be
called?

I am calling PlatformUI.createAndRunWorkbench(display, new
ApplicationWorkbenchWindowAdvisor())

Thanks,
Chris
Previous Topic:xmi version of the workbench model, can these be used to create a workbench?
Next Topic:e4 and Eclipse 3.6
Goto Forum:
  


Current Time: Fri Mar 29 13:36:22 GMT 2024

Powered by FUDForum. Page generated in 0.03635 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top