Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Mixing Plugins and Bundles in RCP
Mixing Plugins and Bundles in RCP [message #33580] Thu, 15 January 2004 15:56 Go to next message
Stephen Goldbaum is currently offline Stephen Goldbaum
Messages: 75
Registered: July 2009
Member
So, I've looked at the RCP tutorials and played with Bundle Projects and
Plugin Projects. I'm still confused on how to mix OSGi bundles with
Equinox generated bundles and/or plugins.

The RCP tutorials are based on implementing an instance of
IPlatformRunnable. However, as far as I can tell there's no hook between
the extensions in this example and the OSGi framework. So how would any
of the views, perspectives, etc. in this tutorial get access to an OSGi
service?

Also, the Export/Import-Package OSGi headers seem to be incompatible with
the Provides-Package Equinox header. Specifically, an bundle deployed
with the Equinox headers won't pick up the classes exported by the OSGi
headers. Similarly, the packages declared with an Import-Package aren't
resolved to those declared with a Provide-Package from another bundle.

This all leads to: How do I cross the divide between pure OSGi bundles and
those generated by Equinox? I seem to be missing how I managed building
the client part of an application using PDE that has access to existing
OSGi bundles.

Thanks,
Stephen
Re: Mixing Plugins and Bundles in RCP [message #33814 is a reply to message #33580] Fri, 16 January 2004 00:13 Go to previous message
Eclipse User
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com

Unfortunately the doc on the new runtime is sparse (but coming). Some
points that may help

- plugin == bundle. There is no difference. It happens that we have a
facility for converting a plugin.xml to a manifest.mf but that is just
syntax and is done automagically/transparently if needed.

- Most of Eclipse does not (yet) define, implement or use services.
Extnesions and extension points are a complementary way of managing the
connections between bundles. Over time we expect Eclipse code to use
services where they are the most appropriate and the extension mechanism
where it makes sense.

- Crossing the divide: PDE is not a BDE (yet). It works mostly in terms of
the things that traditional plugin developers do/need. So, for example, it
does not have a bundle manifest editor which would allow you to express
Imports and Exports. You have to define the manifest.mf yourself. PDE is
still helpful does not yet cover all the cases you will see.

Hope that helps
Jeff


"Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
news:bu6upo$mfo$1@eclipse.org...
> So, I've looked at the RCP tutorials and played with Bundle Projects and
> Plugin Projects. I'm still confused on how to mix OSGi bundles with
> Equinox generated bundles and/or plugins.
>
> The RCP tutorials are based on implementing an instance of
> IPlatformRunnable. However, as far as I can tell there's no hook between
> the extensions in this example and the OSGi framework. So how would any
> of the views, perspectives, etc. in this tutorial get access to an OSGi
> service?
>
> Also, the Export/Import-Package OSGi headers seem to be incompatible with
> the Provides-Package Equinox header. Specifically, an bundle deployed
> with the Equinox headers won't pick up the classes exported by the OSGi
> headers. Similarly, the packages declared with an Import-Package aren't
> resolved to those declared with a Provide-Package from another bundle.
>
> This all leads to: How do I cross the divide between pure OSGi bundles and
> those generated by Equinox? I seem to be missing how I managed building
> the client part of an application using PDE that has access to existing
> OSGi bundles.
>
> Thanks,
> Stephen
>
Previous Topic:OSGi Bundle Fragments and Services
Next Topic:getPackage
Goto Forum:
  


Current Time: Sat Aug 02 00:38:26 EDT 2014

Powered by FUDForum. Page generated in 0.01405 seconds