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) types. > > I have discovered that Castor uses a short when setting > the milliseconds for a duration. > > e.g, consider the following duration string > "P0000Y00M00DT00H00M56.326745125S" > > Castor passes the number "326745125" to it's > Duration.setMillis() method > e.g., result.setMilli((short)number); > > A java short has a max of 32767 or in other words > milliseconds can only be specifed with 4 significant > digits. > > Is this a current limitation of Castor? I tested with Castor 9.5.3. > > ------------------------------------------------------------------------ > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
