<<
From the Schema specification, "dateTime represents a specific instant
of time". Although a timezone-like offset from UTC is allowed in the
representation of a dataTime value, as I understand it this is not part
of the dateTime *value* - in other words, it's just a convenience that
is meant to
[EMAIL PROTECTED] wrote:
Dennis Sosnoski <[EMAIL PROTECTED]> escreveu:
From the Schema specification, "dateTime represents a specific instant
of time". Although a timezone-like offset from UTC is allowed in the
representation of a dataTime value, as I understand it this is not part
of the dateTime
>Dennis Sosnoski <[EMAIL PROTECTED]> escreveu:
> From the Schema specification, "dateTime represents a specific instant
>of time". Although a timezone-like offset from UTC is allowed in the
>representation of a dataTime value, as I understand it this is not part
>of the dateTime *value* - in other
From the Schema specification, "dateTime represents a specific instant
of time". Although a timezone-like offset from UTC is allowed in the
representation of a dataTime value, as I understand it this is not part
of the dateTime *value* - in other words, it's just a convenience that
is meant to
Hi,
In response to "ow"s request for java.util.Date <-> xsd:dateTime
conversion, I have written an Axis sample that uses a custom generator
in WSDL2Java to bind dateTime to java.util.Date instead of
java.util.Calendar. You can download the sample set at [1], the sample
is called StaffLocator.
Not
