Update for those interested.

Seems it's actually the declarative services implementation we're
using that stops working when I set
osgi.compatibility.bootdelegation=false.

Within eclipse it's code in org.eclipse.osgi packages that fails to
import other packages.

MikeG

On 30/01/2008, Thomas Watson <[EMAIL PROTECTED]> wrote:
>
>
> Since this is Equinox specific discussion, could you open a bug against
> Equinox with steps to reproduce? At this point I do not have any ideas why
> boot delegation would effect your ability to load classes from
> org.eclipse.osgi. These classes should not be available from boot to begin
> with.
>
>  Thanks.
>
>  Tom
>
>
>
>  [EMAIL PROTECTED] wrote on 01/30/2008 10:33:52 AM:
>
>
>  > Hi, thanks that all looked promising.
>  >
>  > Unfortunately if I set
> osgi.compatibility.bootdelegation=false in
>  > the config ini for the standalone build my application never gets
>  > anywhere because none of the bundles specified in osgi.bundles get
>  > started. I suspect a NoClassDefFound exception breaks the launcher
>  > or one of the early eclipse bundle startups somewhere but I haven't
>  > found this yet.
>  >
>  > Within eclipse (when I get it to break) If I apply the same property
>  > setting in the run configuration I get NoClassDefFound errors from
>  > code in the org.eclipse.osgi packages.
>  >
>  >
> http://wiki.eclipse.org/index.php/Equinox_Boot_Delegation
> is fairly
>  > informative but I think I've followed it's advice. My bundle imports
>  > org.xml.sax by package (from the xalan bundle). It also imports the
>  > org.osgi.framework, org.osgi.service.event and
>  > org.osgi.service.metatype packages but that shouldn't cause the
>  > wrong packages to get imported. I've tried importing every package
>  > in the xalan bundle in addition to the org.xml.sax package actually
>  > referenced in my code but it doesn't seem to make any difference.
>  >
>  > Setting org.osgi.framework.bootdelegation=false has no
> effect that I
>  > can discern.
>  >
>  > Thanks
>  > MikeG
>  >
>
>
>  > On 30/01/2008, Thomas Watson <[EMAIL PROTECTED]> wrote:
>  > One small correction.
>  >
>  > In Eclipse 3.3 the org.osgi.framework.bootdelegation
> property is
>  > *not* set by default. Unfortunately Eclipse still needs to give boot
>  > access by default to reduce the amount of compatibility issues with
>  > previous versions of Eclipse (and OSGi R3) where everything from
>  > boot came for free. To do this there is a compatibility options
>  > osgi.compatibility.bootdelegation which is set to true
> by default.
>  > This option does a search boot last when enabled. Try setting this
>  > property to false either as a java system property (-
>  > Dosgi.compatibility.bootdelegation=false) or by setting
>  > osgi.compatibility.bootdelegation=false in your
> config.ini.
>  >
>  > Tom
>  >
>  >
>  >
>
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> http://www2.osgi.org/mailman/listinfo/osgi-dev
>


-- 
 - MikeG
_______________________________________________
OSGi Developer Mail List
[email protected]
https://www2.osgi.org/mailman/listinfo/osgi-dev

Reply via email to