XS:Date format incorrectly including time zone
----------------------------------------------
Key: AXIS2-5227
URL: https://issues.apache.org/jira/browse/AXIS2-5227
Project: Axis2
Issue Type: Bug
Components: databinding
Affects Versions: 1.6.1
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.
Reporter: Lucas Holt
Priority: Minor
The time zone is appended to date such as 2011-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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
