Eclipse Community Forums: Eclipse Platform » Visible and not visible classes

Home » Eclipse Projects » Eclipse Platform » Visible and not visible classes

Visible and not visible classes [message #321648]

Tue, 23 October 2007 10:25

Eclipse User

Originally posted by: egidijus.vaisnora.nomagiclt.com

Hello,

I have problems with classes and class visibility within OSGI.
I have a plugin, let call it Eclipse plugin A. This plugins exports his own API for loading some kind of plug-in for himself -
lets call them internal plugins of the Eclipse plugging (IPEP) which have nothing to do with Eclipse plugins. IPEP are loaded
on separate URLClassLoader (I suppose it must has a bundle classloader as a Parent class loader). Problem is that a third part
Eclipse plugin has a dependency on my Eclipse plugin A (it is ok) and also it desires to see classes from the IPEP, but these
classes, loaded by my plugin are not found.
I know, that perhaps IPEP is not proper solution for OSGI platform, but perhaps there is any way to expose classes of IPEP to
whole OSGI platform? I have tried to use "Export-Packages" but not successful. Thank you for your help and time.

Kind Regards,
Egidijus

Re: Visible and not visible classes [message #321651 is a reply to message #321648]

Tue, 23 October 2007 12:55

Eclipse User

Like loading plugins from a different plugin framework within your plugin?

It seems to me that you have a couple of options, perhaps, of ways to
organize your problem to make OSGi happy. You can also ask in
eclipse.technology.equinox, they understand the classloading well:

Make your IPEPs eclipse plugins. Even if they're some other PF
libraries, simply updating the MANIFEST.MF with OSGi headers should be
enough to get eclipse to read them.

Or make the IPEPs fragments with plugin A as the host. They'll be read
into the plugin A OSGi space, and their Export-Packages will be exported
from A.

If you make changes while the system is running, you can use
BundleContext and the PackageAdmin service to "refresh" the list of
packages that other OSGi bundles can see.

And failing that, you can write some kind of classloading hook (a la
http://wiki.eclipse.org/Adaptor_Hooks ) to manipulate the classpath at
the OSGi level.

Later,
PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm

Re: Visible and not visible classes [message #321677 is a reply to message #321651]

Wed, 24 October 2007 03:23

Eclipse User

Originally posted by: egidijus.vaisnora.nomagiclt.com

Thank you, Paul. From your comments I am starting to realize that there are no light "workaround" and my internal plugins
management must be rewritten to support Eclipse bundle interface :(

Previous Topic:	Minimal Width of a TreeColumn - 1 attachment
Next Topic:	treeViewer.setSelection() doesn't work in my case

Goto Forum:

-=] Back to Top [=-

Current Time: Sun May 04 05:28:56 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter