Eclipse Community Forums: Equinox » org.osgi.framework.bootdelegation=*

Help

Home

Home » Eclipse Projects » Equinox » org.osgi.framework.bootdelegation=*

Show: Today's Messages :: Show Polls :: Message Navigator

org.osgi.framework.bootdelegation=* [message #65449]

Thu, 27 April 2006 12:35

David Michonneau

Messages: 1145
Registered: July 2009

Senior Member

Hi,

I would like to prevent the boot delegation to kick in for some of my
bundles, as it causes issues. There are some classes with the same name in
the parent classloader's scope, that I do not want to be loaded by OSGi. I
see that org.osgi.framework.bootdelegation is set to * by default and I read
in https://bugs.eclipse.org/bugs/show_bug.cgi?id=29007 that changing it
might create issues in some JVM. So my question is: how to prevent the
bootdelegation for some plugins if not by this setting? What are exactly
those JVM bugs about?

I am running OSGi equinox outside Eclipse, using the latest version.

Thanks,

David

Report message to a moderator

Re: org.osgi.framework.bootdelegation=* [message #65834 is a reply to message #65449]

Mon, 01 May 2006 20:10

Thomas Watson

Messages: 503
Registered: July 2009

Senior Member

Most of the VM bugs are related to the class libraries provided by the
VM assume that all classloaders in the system have access to everything
on the boot classpath. On area where this was a problem was when using
reflection some of the classes on the boot classpath would use the
calling classloader to load other classes from the boot classpath. This
would result in strange class loading errors. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=92924 for more information.

If you are using equinox as stand-alone then I would suggest you set the
property osgi.java.profile.bootdelegation=none.

See eclipse help for information on this property. Basically this will
result in strict OSGi R4 parent classloader delegation. Unfortunately
Eclipse has many plub-ins/bundles which run on top of it that has
assumed ALL packages are available from the boot classpath. It will
take some time to move everybody off of bootdelegation=* but it is a
goal of ours. As long as you don't have any bundles that assume access
to all boot classpath packages then you should be fine.

Report message to a moderator

Previous Topic:	Eclipse OSGi internal APIs
Next Topic:	OSGI settings missing ....

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 03:00:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter