[SLING-6258] The PackageAdminClassLoader cannot load classes from bundles providing older API versions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons ClassLoader 1.3.2
• Fix Version/s: Commons ClassLoader 1.3.6
• Component/s: Commons
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 08/Nov/16 17:58
• Updated: 04/Sep/19 12:43
• Resolved: 10/Nov/16 15:05

Description

The org.apache.sling.commons.classloader.impl.PackageAdminClassLoader cannot correctly load classes that exist only in bundles providing older API implementations if another bundle providing the same API, but newer version, exists on the instance.

Assuming bundles A and B both export org.example, A with version 1.0.0 and B with version 2.0.0, when the org.apache.sling.commons.classloader.impl.PackageAdminClassLoader is queried to resolve a class only available in A, it will try to resolve it from B. This happens because the org.apache.sling.commons.classloader.impl.PackageAdminClassLoader only checks the bundle that provides the highest API (in terms of version number) of the class' providing package.

Issue Links

• is duplicated by: SLING-6259 The PackageAdminClassLoader cannot load classes from bundles providing older API versions
• links to: GitHub Pull Request #1