axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (AXIS-1399) axis.types.Time does not deserialise properly in UK/GMT0BST
Date Thu, 17 Jun 2004 14:45:09 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: AXIS-1399
    Summary: axis.types.Time does not deserialise properly in UK/GMT0BST
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             Deployment / Registries
             current (nightly)

   Reporter: Steve Loughran

    Created: Thu, 17 Jun 2004 7:44 AM
    Updated: Thu, 17 Jun 2004 7:44 AM
Environment: Java1.4.2 on RH9.0 and Windows XP2 SP2

The axis time class does not properly deserialise a time when running in the UK (at least
on both systems tested)

TestDeser2001.testTimeZoneLogicWorks() demonstrates the problem

The underlying cause appears to be in Time.ParseHoursMinutesSeconds(), where zulu.parse()
takes in a string like "12:30:00Z" and, in the UK, returns a timestamp bound to 13:30:00.

This is quite a serious difference in expectations, and appears to be happening somewhere
we cannot get at. Either it is a TZ issue, a locale issue, a bug in Java1.4.2, or an installation
defect common to two systems (and platforms) under my control. 

I dont have an obvious fix, but I would hesitate to ship with such a deser bug, were time
not such a troublespot already. 

I think the ideal solution may be to abandon the built in simple time parser completely and
do it ourselves, the way we do partially anyway, then write some good tests for the new code.
Too bad we cannot use java1.4 regexp (or C sscanf()) to do the low-level work.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message