Yes. The point is that the package is a complete unit when it is exported or imported. So, in this case, when it does not contain the requested type, you must stop searching as you have a failure to locate the type. This avoids the split package problem. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Francisco Olarte <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2013/11/26 03:39 Subject: Re: [osgi-dev] questions about the bundle class search order Sent by: [email protected] Hi: On Tue, Nov 26, 2013 at 8:21 AM, Anacristing <[email protected]> wrote: > I'm studying osgi.core-5.0 specification. > I don't understand step 6 of search order in the section 3.9.4. > It says: > If the class or resource is in a package that is exported by the bundle or > the package is imported by > the bundle (using Import-Package or Require-Bundle), then the search ends > and the class or > resource is not found. I'm suppossing above text is a direct quote, so... > I think if the class is found in this step, it should be already found in > step 3, 4 or 5. In which case the class is not found in step 3, 4 or 5 but > found here? Note the step does NOT say anything about a class being found, just about the package. This seems to be an stopper, I mean, you have searched for the class in steps above, did not found it but you have the package in the imp/exp, so this step stops you from searching anywhere else, like trying dynamic imports in step 7 ( but only if the class's package meets certain conditions ). Regards. F.O.S. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
