[jira] [Created] (SLING-7582) Configuration for dictionary load order behaviour

["Andreas Haller (JIRA)" <ji...@apache.org>]

Andreas Haller created SLING-7582:
-------------------------------------

             Summary: Configuration for dictionary load order behaviour
                 Key: SLING-7582
                 URL: https://issues.apache.org/jira/browse/SLING-7582
             Project: Sling
          Issue Type: Improvement
          Components: i18n
    Affects Versions: i18n 2.5.12
            Reporter: Andreas Haller


Like stated in [the documentation|https://sling.apache.org/documentation/bundles/internationalization-support-i18n.html#resourcebundle-hierarchies] and [the source code|https://github.com/apache/sling-org-apache-sling-i18n/blob/master/src/main/java/org/apache/sling/i18n/impl/JcrResourceBundle.java#L167] the load order of i18n dictionaries follows the ResourceResolvers search paths and is: /<others>, /libs, /apps which means /libs overrides /<others> and /apps overrides /libs. While I like the idea of using the search paths for loading dictionaries we have regularly the requirement of maintaining i18n dictionaries outside of /apps, see also https://issues.apache.org/jira/browse/SLING-4344?focusedCommentId=14297818&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14297818

Considering this, in my opinion it would make sense to have a configuration option to load /<others> after /libs and /apps and having the possibility to override the applications out-of-the-box translations by dictionaries outside of the search path. My proposal is to extend the configuration of JcrResourceBundleProvider giving paths not on the search path (e.g. /content) priority over /libs and /apps.



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