Hi Bowden,
Looks like it might be a problem! :-)
Can you file a bug report on that (http://bugzilla.exolab.org).
Thanks,
--Keith
"Wise, Bowden (Research)" wrote:
>
> I resent my original query as plaintext below as requested:
>
> I have a schema that uses durations (e.g., xs:duration) type
Hi,
can you please resend your email to this mailing list as text/plain rather than
text/html or something similar ? I do not want to come across impolite, but I'd
rather you followed the mailing list guidelines as defined at
http://castor.exolab.org/lists.html#Guidelines
in general and htt
I have a schema that uses durations (e.g., xs:duration) types.
I have discovered that Castor uses a short when setting
the milliseconds for a duration.
e.g, consider the following duration string
"PY00M00DT00H00M56.326745125S"
Castor passes the number "326745125" to it's
Duration.setMillis(
Here is my original question posted as plain text:
I have a schema that uses durations (e.g., xs:duration) types.
I have discovered that Castor uses a short when setting
the milliseconds for a duration.
e.g, consider the following duration string
"PY00M00DT00H00M56.326745125S"
Castor passe
Hi,
can you please resend your question to this mailing list as plain text, i.e.
text/plain and not text/html ?
Regards
Werner
On Thu, 6 May 2004 17:06:04 -0400, Wise, Bowden (Research) wrote:
>---
>If you wish to unsubscribe from this
Hi
I have a schema that uses durations (e.g., xs:duration) types.
I have discovered that Castor uses a short when setting
the milliseconds for a duration.
e.g, consider the following duration string
"PY00M00DT00H00M56.326745125S"
Castor passes the number "326745125" to it's
Duration.setMil
