Re: [equinox-dev] Re: ContextFinder stops at first bundle class loader
> I know about buddy class loading. But I want to avoid it. If the context > finder would look further up the stack and not abort on the first bundle > class loader it finds things would actually work without buddy class > loading. I was just wondering if the context finder could be (or should > not be) enhanced to support this. > > -Gunnar The design of ContextFinder is to be policy free. The policy comes from the OSGi delegation model + the Equinox buddy policy. We should avoid building such a policy into the ContextFinder. It is inevitable that there are scenarios where a built in policy would not work. The policy should be specified by the bundle (e.g. DynamicImport-Package, Eclipse-BuddyPolicy etc.) and not kept in a global ContextFinder TCCL. Tom.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Re: ContextFinder stops at first bundle class loader
Thomas, Thanks for your reply. Thomas Watson wrote: > I try to avoid DynamicImport-Package as much as possible because it has > several drawbacks (like risk of replacing any of your private classes > including your bundle activator from other exporters!!). Instead you > should try using the buddy classloading mechanism. Adding the following > header should give you the behavior you are looking for: I know about buddy class loading. But I want to avoid it. If the context finder would look further up the stack and not abort on the first bundle class loader it finds things would actually work without buddy class loading. I was just wondering if the context finder could be (or should not be) enhanced to support this. -Gunnar -- Gunnar Wagenknecht [EMAIL PROTECTED] http://wagenknecht.org/ ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
