[SLING-7429] Improve basename handling

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: i18n 2.5.12
• Component/s: i18n
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 23/Jan/18 12:46
• Updated: 25/Oct/19 18:24

Description

Right now the basename handling according to https://sling.apache.org/documentation/bundles/internationalization-support-i18n.html#resourcebundle-with-base-names is as follows

The base name argument can take one three values:

1. null, selects messages of mix:language nodes ignoring the existence or absence of sling:basename properties
2. Empty String, selects messages of mix:language nodes which have sling:basename properties, ignoring the actual values
3. Any other Value, selects messages of mix:language nodes whose sling:basename properties has any value which matches the base name string

I think it should somehow be also possible for a client to explicitly select a resource bundle which is not having the sling:basename property set.

This was originally triggered from https://issues.apache.org/jira/browse/SLING-7421?focusedCommentId=16335686&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16335686.

Issue Links

• is related to: SLING-8802 JcrResourceBundle should not consider dictionaries with a basename, if no basename is provided
• relates to: SLING-7430 Invalid assumptions in SlingSpecificsSightlyIT#testI18nBasename