You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Carl-Eric Menzel (JIRA)" <ji...@apache.org> on 2016/11/25 13:09:58 UTC

[jira] [Resolved] (WICKET-6273) Wicket should use the appropriate Locale for the context

     [ https://issues.apache.org/jira/browse/WICKET-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl-Eric Menzel resolved WICKET-6273.
--------------------------------------
    Resolution: Fixed

> Wicket should use the appropriate Locale for the context
> --------------------------------------------------------
>
>                 Key: WICKET-6273
>                 URL: https://issues.apache.org/jira/browse/WICKET-6273
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 7.4.0, 8.0.0-M2
>            Reporter: Carl-Eric Menzel
>            Assignee: Carl-Eric Menzel
>            Priority: Minor
>
> On some systems (like my desktop ;-) ) there is not one single Locale, but rather different ones for text and formats. For example, I use en_US for nearly everything, but de_DE for formatting. In this situation, DurationTest fails, because DurationTest correctly uses NumberFormat.getNumberInstance, which uses Locale.getDefault(Locale.Category.FORMAT). Duration itself, however, just calls Locale.getDefault() and thus misses the difference. 
> This is likely not an problem in production, since from the request and the session there is only one single locale per user anyway. But in testing and developing, this might sometimes be an issue. Best to also check the other uses of Locale.getDefault in the codebase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)