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=12339>. 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=12339 xsd:date fails to un-marshal on reply because the de-serializer is expecting a time. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2002-09-18 15:52 ------- The runtime is using the CalendarSerializer/Deserializer instead of the Date. The happens on both client and server side. The reason is that when looking up types in the DefaultTypeMapping by class, the Date class is registered as both xsd:date and xsd:datetTime. In this case, the dateTime mapping is registered last, so it is used. The meta-data for the fields in a JavaBean should include the XML type. There is a field for this in the FieldDesc class, but it was never set/used. The runtime should then use this when looking up the type.
