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

Robert Godfrey updated QPID-8105:
---------------------------------
    Description: 
The tests make assumptions that they are running in a Locale where the comma 
character is used to separate thousands in long numbers, and the dot character 
is used to separate whole numbers from decimal fractions.  

There are two types of errors, one where numbers are formatted in the tests 
using the default Locale, but compared to output from the Broker messages which 
always use Locale.US.  Secondly there are tests which assume the output value 
from the Broker will always be in a Locale.US format, but are actually 
determined by the current Locale inside the broker (e.g. in the HTTP management 
API, and in storing JSON).

> broker-core unit tests are failing because of wrong locale
> ----------------------------------------------------------
>
>                 Key: QPID-8105
>                 URL: https://issues.apache.org/jira/browse/QPID-8105
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.1
>            Reporter: Olivier VERMEULEN
>            Priority: Major
>
> The tests make assumptions that they are running in a Locale where the comma 
> character is used to separate thousands in long numbers, and the dot 
> character is used to separate whole numbers from decimal fractions.  
> There are two types of errors, one where numbers are formatted in the tests 
> using the default Locale, but compared to output from the Broker messages 
> which always use Locale.US.  Secondly there are tests which assume the output 
> value from the Broker will always be in a Locale.US format, but are actually 
> determined by the current Locale inside the broker (e.g. in the HTTP 
> management API, and in storing JSON).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to