Hi: > Suppose the class is not found, but I have the package in the imp using > Import-Package, then I think the searching should be stopped after step 3. > Because, if the package in the imp, the request of loading class is > delegated to an exporting class loader, and in step 3 it says: > If the request is delegated to an exporting class loader and the class or > resource is not found, then the search terminates and the request fails. > Right?
I cannot assure you, as I'n not that knowledgeable in this things. Were I to implement a framework my first thought is that "Frameworks must adhere to the following rules for class or resource loading." could be satisfied even discarding the import package part of " or the package is imported by the bundle (using Import-Package or Require-Bundle)" on point 6 as it seems to be shortcircuited by step 3, but I'll probably implement the check anyway and opimitize it out later after careful analysis. It seems to be a harmless redundancy put there with the intent to clarify things, or perhaps the writer did not notice step 3 is terminal but step 4 is not, or some more rewriting is needed. F.O.S. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
