[jboss-jira] [JBoss JIRA] (WFLY-3723) setting the local to english in CLI commands on non-english systems does not produce english output

[Romain Pelisse (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029555#comment-13029555 ] 

Romain Pelisse commented on WFLY-3723:
--------------------------------------

Ok, I've found out the root cause. The issue is that when one ask for en_US, it does find any bundled resources with this prefix - because this is considered the default (hence no appropriate extension):

$ find . -name "LocalDescriptions*" | grep org.jboss.as.pojo.LocalDescriptions 
./pojo/src/main/resources/org/jboss/as/pojo/LocalDescriptions_de.properties
./pojo/src/main/resources/org/jboss/as/pojo/LocalDescriptions_fr.properties
./pojo/src/main/resources/org/jboss/as/pojo/LocalDescriptions.properties   ==> This one contains 'en_US' but not the extension
....

However, as default is French (or German), when ask specifically for en_US, no bundle is found, and the JDK falls back to the default Locale (FR or DE), not English. 

IMHO, the best way to fix that would be to modify the build to copy './pojo/src/main/resources/org/jboss/as/pojo/LocalDescriptions.properties' into ./pojo/src/main/resources/org/jboss/as/pojo/LocalDescriptions.properties_en'. There would be duplication, but only in the generated artefact, and it does sound less cumbersome than having to modify Wildfly code to handle this 'edge cases'.

Or maybe someone has a better idea ?


> setting the local to english in CLI commands on non-english systems does not produce english output
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3723
>                 URL: https://issues.jboss.org/browse/WFLY-3723
>             Project: WildFly
>          Issue Type: Bug
>          Components: Localization
>    Affects Versions: 8.1.0.Final
>         Environment: Tested on MacOS running in German
>            Reporter: Tom Fonteyne
>            Assignee: Romain Pelisse
>            Priority: Minor
>
> A German (or french etc...) system must be used to reproduce.
> It is likely this is not limited to MacOS, but I do not have a non-english Linux system available
> An out of the box install of wildfly/EAP:
> Without configuration, the log file is in German as expected.
> Using these CLI comands:
> :read-operation-description(name=stop-servers,locale=de_DE) -> german
> :read-operation-description(name=stop-servers,locale=en_US) -> german
> :read-operation-description(name=stop-servers,locale=fr_FR) -> french
> So we cannot get the CLI to produce english output
> when configuring JAVA_OPTS in domain.conf with:
> JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.country=DE -Duser.encoding=utf-8
> The log is now in English -> works as expected; and:
> :read-operation-description(name=stop-servers,locale=de_DE) -> german
> :read-operation-description(name=stop-servers,locale=en_US) -> english
> So it seems we have a bug where the locale set to start the domain takes precedence over the locale set in the CLI command (but only when English is asked)
> I presume this is because English is the default locale.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)