| osgi bootdelegation [message #668355] |
Thu, 05 May 2011 07:31  |
Eclipse User |
|
|
|
In my test case, Equinox is launched using the standard R4.2 launcher API. The properties object passed to create a framework instance does NOT contain osgi.compatibility.bootdelegation property. I expected it to be defaulted to false and bootdelegation to only happen for whatever packages are configured via org.osgi.framework.bootdelegation property. It seems I am wrong. Unless I set osgi.compatibility.bootdelegation to false, it seems to be getting set to true, as I see some classes getting loaded from parent class loader although their packages are not configured in the standard bootdelegation property. When I explicitly set it to false, I don't see such classes getting loaded from parent class loader. Am I wrong in concluding this to be a bug in Equinox, as why should I be required to use a non-standard property to get spec compliant behavior when I am using R4.2 launcher API? I am using Equinox 3.6.1.
Thanks,
Sahoo
|
|
|
|
Powered by
FUDForum. Page generated in 0.04056 seconds
Home