Hi: On Tue, Nov 26, 2013 at 2:50 PM, BJ Hargrave <[email protected]> wrote:
> 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. > Probably the process could be easier to understand if it was split in get target package / get class in package. To load a class resource then locate a package using steps 1..8, if no package is found, resource not found. If package found and class there, found, else not found. Maybe with a remark 'class must be looked up in the first found package and no further'. And maybe my copy of 5-core is out of date, but to further complicate things the non-normative flow chart is numbered 1-9, not 1-8, and looks like it starts diverging just in 6, which coupled with that chapter being a non-trivial one can complicate a lot the reading. F.O.S.
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
