Eclipse Community Forums: Equinox » Issue with Non OSGi eclipse bundles

Home » Eclipse Projects » Equinox » Issue with Non OSGi eclipse bundles

Issue with Non OSGi eclipse bundles [message #894804]

Tue, 10 July 2012 11:04

Eclipse User

Hello,

We are using the Virgo Server to build an OSGi based web application. Everything works fine as long as we have our bundle implementation which is targeted to run with OSGi framework.

We now have to use some legacy eclipse plugins which were initially targeted to run with eclipse. These are implemented as Eclipse Plugins which do not follow the OSGi specifications. Since many of them use the eclipse framework related plugins and VIRGO server is not able to start the eclipse bundles, we are facing the problem with this integration.

Could anyone please help us out.Thanks in advance for help.

~Murthy

P.S: I have also posted this in Virgo forum, but wanted to get an opinion from here as well.

Re: Issue with Non OSGi eclipse bundles [message #894812 is a reply to message #894804]

Tue, 10 July 2012 11:45

Eclipse User

Could you describe more the kind of problems you are running into? Do you mean that those bundles don't have a manifest?

Re: Issue with Non OSGi eclipse bundles [message #894879 is a reply to message #894804]

Tue, 10 July 2012 17:45

Eclipse User

Hello Murphy,
it would be not easy to migrate Eclipse **Platform** plug-ins to pure
OSGi bundles. I did similar a few weeks ago (but I've migrated Platform
plug-ins to pure Equinox bundles).

Borders are not always clear and if plug-ins are depend on being
(org.eclipse.core.runtime.Platform.isRunning() == true) a lot of work is
waiting to you (or it can be even impossible).

Either way, I'm looking forward if you will share your experience.

Libor

On 07/10/2012 05:04 PM, Murthy Bhat wrote:
> Hello,
>
> We are using the Virgo Server to build an OSGi based web application.
> Everything works fine as long as we have our bundle implementation which
> is targeted to run with OSGi framework.
> We now have to use some legacy eclipse plugins which were initially
> targeted to run with eclipse. These are implemented as Eclipse Plugins
> which do not follow the OSGi specifications. Since many of them use the
> eclipse framework related plugins and VIRGO server is not able to
> start the eclipse bundles, we are facing the problem with this integration.
> Could anyone please help us out.Thanks in advance for help.
>
> ~Murthy
>
>
> P.S: I have also posted this in Virgo forum, but wanted to get an
> opinion from here as well.

Re: Issue with Non OSGi eclipse bundles [message #894928 is a reply to message #894879]

Wed, 11 July 2012 02:42

Eclipse User

Thanks Libor. Will share our approach with you as soon as we have one Smile

@Pascal: Below is the problem we are running into

1. There are some legacy eclipse plugins which were intended to run as a RCP application. But they all have MANIFEST files.
2. The activator for these plugin extends from 'AbstractUIPlugin' (org.eclipse.ui.plugin).
3. Hence an eclipse environment is required to start this plugin.
4. Also the legacy plugins are mainly Extension point based.
5. The plugin also makes use of the eclipse workbench and PlatformUI api.

Our current application is an OSGi based web application where we try to deploy it onto Virgo Tomcat OSGi container. It is a service based approach where bundles provide/consume OSGi services. When executed, the Virgo server complains and does not start the UI related plugins because they can only be invoked by eclipse runtime.

So without modifying the legacy eclipse plugins, is there a way to integrate it along with the other OSGi bundles.

Thanks for help.

~Murthy

Re: Issue with Non OSGi eclipse bundles [message #895371 is a reply to message #894928]

Thu, 12 July 2012 11:19

Eclipse User

If they have MANIFESTs they are OSGi bundles (as well as being eclipse plugins), they just require the org.eclipse.ui set of bundles to be included as well (the UI workbench + SWT, the equinox registry bundle, etc).

Since your plugins require workbench (UI) services to run, you won't be able to include them in a Virgo server unless you can 1) launch an entire workbench in the server, which doesn't make sense or 2) refactor your plugins so the differentiate between core services (headless) and UI services.

PW

Previous Topic:	Problems with equinox console in 4.2M4
Next Topic:	NPE when deploying OSGi app with p2 director

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 07:30:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter