Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-5227

XS:Date format incorrectly including time zone

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.6.1
    • Fix Version/s: None
    • Component/s: databinding
    • Labels:
      None
    • Environment:
      Reverse engineered web service was generated for the COUNTER 4 SUSHI specification on OpenJDK 6 / FreeBSD/ Tomcat 7 using command line tools included with Axis 2 to generate from WSDL.

      Description

      The time zone is appended to date such as 2011-01-01 -05:00. According to ISO 8601, date formats do not include time zones, only date time types do.

      This issue is caused by apache xmlbeans in the way it converts dates. This bug report covers the details. I think code generated from AXIS2 should use one of the workarounds or request that this bug be fixed in xmlbeans.

      https://issues.apache.org/jira/browse/XMLBEANS-242

      I think the confusion was caused by http://www.w3.org/TR/xmlschema-2/#date They show examples of this incorrect date format, but when looking at the 3.2.9.1 Lexical representation section, you can see that it implies datetime (and thus ISO8601) rules apply for date formats. The w3 document was referenced in the soap document here http://www.ws-i.org/profiles/BasicProfile-1.0-2004-04-16.html

      The root problem for me is that this inconsistency puts me out of compliance with COUNTER http://www.projectcounter.org/code_practice.html and possibly will cause interoperability issues with .NET clients from what I've read.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              laffer1 Lucas Holt
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: