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

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2019/04/16 13:55:00 UTC

[jira] [Created] (SLING-8356) Increase service.ranking of ResourceTypeBasedResourcePicker

Konrad Windszus created SLING-8356:
--------------------------------------

             Summary: Increase service.ranking of ResourceTypeBasedResourcePicker
                 Key: SLING-8356
                 URL: https://issues.apache.org/jira/browse/SLING-8356
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: Sling Models Impl 1.4.10
            Reporter: Konrad Windszus
             Fix For: Sling Models Impl 1.4.12


Currently the {{ResourceTypeBasedResourcePicker}} (https://github.com/apache/sling-org-apache-sling-models-impl/blob/master/src/main/java/org/apache/sling/models/impl/ResourceTypeBasedResourcePicker.java#L34) is always the 2nd last picker and the {{FirstImplementationPicker}} (https://github.com/apache/sling-org-apache-sling-models-impl/blob/master/src/main/java/org/apache/sling/models/impl/FirstImplementationPicker.java#L36) is the last picker.

In some cases you are interested to place pickers in between (compare with https://github.com/adobe/aem-core-wcm-components/issues/546), therefore I would propose to set the {{service.ranking}} of {{ResourceTypeBasedResourcePicker}} to {{(Integer.MAX_VALUE - 1000)}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)