[
https://issues.apache.org/jira/browse/SLING-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678718#action_12678718
]
Bertrand Delacretaz commented on SLING-877:
-------------------------------------------
Agree with Jukka that not doing any checks seems reasonable.
Do you know what's specified to happen if calling new Locale("foo", "bar") and
there's no foo_bar locale available?
In a quick test I seem to get the VM's default locale in that case, but the
Locale javadocs don't specify this case.
> Avoid calling Locale.getAvailableLocales() because it is very slow
> ------------------------------------------------------------------
>
> Key: SLING-877
> URL: https://issues.apache.org/jira/browse/SLING-877
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Thomas Mueller
> Attachments: JcrResourceBundleProvider.patch
>
>
> Currently, JcrResourceBundleProvider.toLocale calls
> Locale.getAvailableLocales().
> The first call to this method is very slow (3.4 seconds on my machine) because
> it scans many jar files.
> http://svn.apache.org/viewvc/incubator/sling/trunk/bundles/extensions/i18n/src/main/java/org/apache/sling/i18n/impl/JcrResourceBundleProvider.java?view=markup
> It looks like calling this method is not required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
