[SLING-8356] Decrease service.ranking of ResourceTypeBasedResourcePicker

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Models Impl 1.4.10
• Fix Version/s: Models Impl 1.4.12
• Component/s: Extensions
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 16/Apr/19 13:54
• Updated: 31/May/19 12:53
• Resolved: 31/May/19 12:53

Description

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).