axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22999] - xs:date not serialized/deserialized correctly
Date Mon, 08 Sep 2003 17:42:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22999>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22999

xs:date not serialized/deserialized correctly

apache@hunterfam.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From apache@hunterfam.com  2003-09-08 17:42 -------
I see the portion of the JAX-RPC spec to which you are referring. The problem is
that axis maps both xs:date and xs:datetime to java.util.Date. The XML Schema
Spec defines date in 3.2.9 of "XML Schema Part 2: Datatypes" as:

[Definition:]  date represents a calendar date. The ·value space· of date is the
set of Gregorian calendar dates as defined in § 5.2.1 of [ISO 8601].
Specifically, it is a set of one-day long, non-periodic instances e.g. lexical
1999-10-26 to represent the calendar date 1999-10-26, independent of how many
hours this day has.

So, when I specify a date in my XML schema, my reading of the above definition
leads me to believe that there should be not time component. If I wanted the
time component, I would have selected xs:datetime. This seems to be the same
assumption that castor made.

Mime
View raw message