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

Samisa Abeysinghe resolved AXIS2C-1500.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0
         Assignee: Samisa Abeysinghe

Applied the provided patch. Thanks for the patch, 

Committed revision 1163206.

> date_time serialize may use invalid separator for milliseconds
> --------------------------------------------------------------
>
>                 Key: AXIS2C-1500
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1500
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>    Affects Versions: Current (Nightly)
>         Environment: OS: Windows 7, Windows Server 2003, 
> Compiler: Visual Studio 2010 (VC10) 
> 32-bit build
>            Reporter: Ivan Pechorin
>            Assignee: Samisa Abeysinghe
>            Priority: Minor
>             Fix For: 1.7.0
>
>         Attachments: axutil_date_time_millis_separator.patch
>
>
> Axis2/C date/time serialization routines in util/src/date_time.c use sprintf. 
> This may lead to comma used as separator between seconds and milliseconds, 
> due to locale settings. I'm not sure if sprintf is locale-dependent on 
> Windows only, or this behavior also exists on other platforms. 
> The standard mandates use of dot (".") as separator, comma is not allowed: 
> http://www.w3.org/TR/xmlschema-2/#dateTime
> Affected routines: 
>  - axutil_date_time_serialize_time 
>  - axutil_date_time_serialize_time_with_time_zone 
>  - axutil_date_time_serialize_date_time 
>  - axutil_date_time_serialize_date_time_with_time_zone 
> I believe, serialize should provide valid (as per standard) output, no matter 
> which separator is specified in locale.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to