If your bundle has an import for that package (com.sun.jdmk.comm) the package has to be resolved by the framework, hence it must be exported by a bundle so by adding the package to the list of system packages, the package will be resolved. Just adding com.sun.* or something like that to boot delegation will not be enough, as this is just about how the classes are loaded. From the specs, to me, it sounds as an expected behavior. Not 100%sure but if you would add to that import, that the package is optional the boot delegation should work. And will work for sure if the import is not present at all.
On Tue, Oct 14, 2008 at 10:39 AM, Rob Walker <[EMAIL PROTECTED]> wrote: > Getting a few unresolved constraints thrown e.g. > > ERROR: Error starting file:e:\data\tas/lib/tas/testrunner.jar > (org.osgi.framewor > k.BundleException: Unresolved constraint in bundle 27: package; > (package=com.sun > .jdmk.comm)) > > If I manually add this to the bootdelegation property, it doesn't get picked > up. > > Adding it to the regular system packages properties gets rid of the error. > > Wondering if the above property is not yet working and/or maybe the .* > wildcard/regex aspect isn't wired in? > > Will carry on investigating - see if I can see the cause. > > -- Rob > > > Ascert - Taking systems to the Edge > [EMAIL PROTECTED] > +44 (0)20 7488 3470 > www.ascert.com > > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
