> 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'.
Except Require-Bundle and it's support for split packages complicate things. So you cannot simplify this to find package then find type. > 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. Yes, I guess that could be improved. That is why the flowchart is non-normative :-) Class loading (to be implemented by frameworks) is complicated with support for parent class loader, boot delegation, package export/import, require-bundle and split packages, bundle-classpath, fragments, dynamic import packages, ... :-) -- 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
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
