[
https://issues.apache.org/jira/browse/SLING-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-2918:
-------------------------------------
Description:
The I18NFilter currently takes the first [Request]LocaleResolver service
available to off-load extraction of the Locale(s) during request processing.
Considering some deployment has a default service installed which should be
superceded by a different implementation on a customized deployment, it would
be nice to be able to replace the existing service with the different
implementation leveraging the service.ranking functionality.
To enable replacement of a service by service.ranking, the DS reference must be
declared with the "greed" policy option.
was:In the Granite environment a RequestLocaleResolver exists by default. If
you install a bundle with another RequestLocaleResolver, it will be ignored -
even if it has a higher ranking - because the dependency has already been
resolved. This could be fixed easily with adding
policyOption=ReferencePolicyOption.GREEDY to the reference.
> I18NFilter ignores RequestLocaleResolver with higher ranking
> ------------------------------------------------------------
>
> Key: SLING-2918
> URL: https://issues.apache.org/jira/browse/SLING-2918
> Project: Sling
> Issue Type: Improvement
> Affects Versions: i18n 2.2.4
> Environment: Granite
> Reporter: Joel Richard
>
> The I18NFilter currently takes the first [Request]LocaleResolver service
> available to off-load extraction of the Locale(s) during request processing.
> Considering some deployment has a default service installed which should be
> superceded by a different implementation on a customized deployment, it would
> be nice to be able to replace the existing service with the different
> implementation leveraging the service.ranking functionality.
> To enable replacement of a service by service.ranking, the DS reference must
> be declared with the "greed" policy option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
