You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by Stefan Seifert <ss...@pro-vision.de> on 2017/10/12 15:19:27 UTC

[adapter] wrong service ranking in AdapterManager implementation

see https://issues.apache.org/jira/browse/SLING-7194 for details.

does anyone has a clue if the current implementation that favors services with lowest ranking when picking the adapter factory if multiple exists was done by intention? i would assume the same logic which is done by BundleContext.getServiceReference().

stefan