You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Kamishima, Kiyoshi (JIRA)" <ji...@apache.org> on 2014/09/19 03:08:34 UTC

[jira] [Created] (WSS-513) Fails to parse Timestamp headers in Thai locale

Kamishima, Kiyoshi created WSS-513:
--------------------------------------

             Summary: Fails to parse Timestamp headers in Thai locale
                 Key: WSS-513
                 URL: https://issues.apache.org/jira/browse/WSS-513
             Project: WSS4J
          Issue Type: Bug
          Components: WSS4J Core
    Affects Versions: 1.6.16
         Environment: Java runtimes running under the th_TH locale
We experienced it on Windows but it should be OS independent.
            Reporter: Kamishima, Kiyoshi
            Assignee: Colm O hEigeartaigh
            Priority: Critical


In Thai, they seem to be using the Buddhist calendar and JRE defaults to using it. And the SimpleDateFormatter ctor which takes only a pattern uses the default locale to see which calendar system to use.
http://docs.oracle.com/javase/7/docs/technotes/guides/intl/calendar.doc.html
http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html

You can see how the API works like this:
>jrunscript -J-Duser.language=th -J-Duser.country=TH -e "println( new java.text.SimpleDateFormat('yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'').parse('2014-01-01T00:00:00.000Z').toString() )"
Tue Jan 01 00:00:00 JST 1471

On the other hand, org.apache.ws.security.util.XmlSchemaDateFormat.parse() always expects the Gregorian calendar is used. If that is the case, it should have configured the formatter with a fixed locale regardless of the default locale.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org