Hi, I see framework doesn't import packages then I must have been mistaken. Running within eclipse is only a development convenience for us so I don't have the time right now to produce any kind of reliable bug report. My investigations have concentrated on our standalone equinox deployment.
In the deployment envronment setting bootdelegation false stops some of our declarative services working. Most likely due to unreported missing imports which I'll track down at a later date. Re just getting something working I've tried many many combinations of bootdelegation and package import specifications with mixed results. It seems to me that the interactions of the jaxp implementation finder, osgi classloading and java endorsed extensions are too complex to figure out in a hurry. We've decided that the practical solution is to just use a completely different xslt library which is known to work in our environment. Deadlines, and life in general being just too short. Sorry I can't provide much more information at this stage, thanks for the help and advice. MikeG On 18/02/2008, Thomas Watson <[EMAIL PROTECTED]> wrote: > > Mike, > > Did you open a bug against Equinox about this issue? I'm not sure what you > mean by org.eclipse.osgi packages that fails to import other packages. The > org.eclipse.osgi bundle is the Framework implementation and cannot import > packages from other bundles. > > Tom > > > > [image: Inactive hide details for "Mike Gould" ---02/18/2008 07:23:17 > AM---Update for those interested.]"Mike Gould" ---02/18/2008 07:23:17 > AM---Update for those interested. > > > From: > "Mike Gould" <[EMAIL PROTECTED]> > To: > "OSGi Developer Mail List" <[email protected]> > Date: > 02/18/2008 07:23 AM > Subject: > Re: [osgi-dev] Problem using xalan and endorsed extensions clash > ------------------------------ > > > > 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 > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://www2.osgi.org/mailman/listinfo/osgi-dev > > -- - MikeG
_______________________________________________ OSGi Developer Mail List [email protected] https://www2.osgi.org/mailman/listinfo/osgi-dev
