It seems that since the upgrade to the final schema standard, Duration's
may no longer be of zero length.  For example,

  P0Y0M0DT0H0M

should be a valid duration, but org.exolab.castor.types.Duration throws
an illegal arg exception at line #118 while complaining that there must
be at least one non-zero component.  Is this a Castor bug?


--
[EMAIL PROTECTED]
Senior Staff Engineer
Institute for Software Integrated Systems
Vanderbilt University
http://www.isis.vanderbilt.edu

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to