You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2016/11/24 16:32:58 UTC
[jira] [Closed] (SLING-6259) The PackageAdminClassLoader cannot
load classes from bundles providing older API versions
[ https://issues.apache.org/jira/browse/SLING-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu closed SLING-6259.
-------------------------------
> The PackageAdminClassLoader cannot load classes from bundles providing older API versions
> -----------------------------------------------------------------------------------------
>
> Key: SLING-6259
> URL: https://issues.apache.org/jira/browse/SLING-6259
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.3.2
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: Commons ClassLoader 1.3.6
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)