You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Brent Cerrato <br...@mosaicsoftware.com> on 2002/12/09 20:52:14 UTC
Datatype change
I have just noticed that Serializing a Date now produces a xsd:dateTime element, as opposed to a xsd:timeInstant element like it used to produce.
What object produces a timeInstant now?
~brent cerrato
Re: Datatype change
Posted by Scott Nichol <sn...@scottnichol.com>.
timeInstant does not exist in the 2001 XML Schema spec. If you need to
generate a timeInstance, you need to use a SOAPMappingRegistry based on
the 1999 or 2000 XML Schema.
Scott Nichol
----- Original Message -----
From: "Brent Cerrato" <br...@mosaicsoftware.com>
To: <so...@xml.apache.org>
Sent: Monday, December 09, 2002 2:52 PM
Subject: Datatype change
I have just noticed that Serializing a Date now produces a xsd:dateTime
element, as opposed to a xsd:timeInstant element like it used to
produce.
What object produces a timeInstant now?
~brent cerrato
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Datatype change
Posted by Scott Nichol <sn...@scottnichol.com>.
timeInstant does not exist in the 2001 XML Schema spec. If you need to
generate a timeInstance, you need to use a SOAPMappingRegistry based on
the 1999 or 2000 XML Schema.
Scott Nichol
----- Original Message -----
From: "Brent Cerrato" <br...@mosaicsoftware.com>
To: <so...@xml.apache.org>
Sent: Monday, December 09, 2002 2:52 PM
Subject: Datatype change
I have just noticed that Serializing a Date now produces a xsd:dateTime
element, as opposed to a xsd:timeInstant element like it used to
produce.
What object produces a timeInstant now?
~brent cerrato
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>