[
https://issues.apache.org/jira/browse/SLING-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584253#comment-13584253
]
Endolf commented on SLING-2536:
-------------------------------
The problem is that there is no bundle for sv, so you get the default, which
might be en, yet getLocale() return sv, which is wrong and not what the
contract of the method says it should do.
We worked around it by having a key in all our bundles that have the language
for that bundle in it, so we could get the language code another way and then
look up the correct locale, but this is not the right way to do it.
> JcrResourceBundle breaks the contract of getLocale
> --------------------------------------------------
>
> Key: SLING-2536
> URL: https://issues.apache.org/jira/browse/SLING-2536
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: i18n 2.2.2
> Reporter: Endolf
>
> The javadoc for getLocale state that it should return the locale of this
> bundle or the locale of the fallback. Currently JcrResourceBundle always
> returns the requested locale even if there is no mix:language for that locale.
> e.g. Only a mix:language with a jcr:language en is in the jcr, a request for
> a resource bundle of sv will return a ResourceBundle object where getLocale
> returns sv. This should return en according to the javadoc.
--
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
