[jira] [Updated] (WICKET-6898) StringResourceModel does not respect getLocale for messages

["Sven Meier (Jira)" <ji...@apache.org>]

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

Sven Meier updated WICKET-6898:
-------------------------------
    Issue Type: Improvement  (was: Bug)
      Priority: Minor  (was: Major)

StringResourceModel#getLocale() is documented as "The locale to use when formatting the resource value".

As I understand it this is meant to be used for formatting the *values* with the MessageFormat only.

If you want to use a different locale for everthing, why don't you override Component#getLocale() instead?

> StringResourceModel does not respect getLocale for messages
> -----------------------------------------------------------
>
>                 Key: WICKET-6898
>                 URL: https://issues.apache.org/jira/browse/WICKET-6898
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-core
>    Affects Versions: 9.3.0, 8.12.0
>            Reporter: Tobias Haupt
>            Priority: Minor
>
> WICKET-5668 states that StringResourceModel has a method getLocale that can be overwritten to provide a custom locale when the messages should be differently localized than the context (Component, Session, default) states.
> The method getString only uses the custom locale when parsing the message with MessageFormat but not to retrieve the message from the Localizer. The locale parameter is null there (Lines 439, 445 / wicket9)
> In my usecase I use the StringResourceModel without a component but want't to provide a custom locale. Instead the Locale.defaultLocale is used to resolve the ressource.
> *Solution:* use the custom Locale getLocal() as parameter for localizer.getString. (The resolving of the locale is implemented the same way in StringResourceModel.getLocale and Localizer.getStringIgnoreSettings anyway.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)