That's actually correct. Before releases 1.1, Castor XML produced 'int' members for <xs:integer> XML artefacts, which was too restrictive with regards to the value range as required by the specification.
Werner > -----Ursprüngliche Nachricht----- > Von: Ralf Joachim [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 12. April 2007 22:17 > An: [EMAIL PROTECTED] > Betreff: Re: [castor-dev] Castor IntegerValidator: Long/Integer bug > > Hi Rudolf, > > the java type for xs:Integer has been changed from int to long with one > of the last releases as the XML schema specification requires at minimum > the value range of java long for an xs:Integer. > > Regards > Ralf > > > Rudolf Wöhrl schrieb: > > Hi, > > > > you most probably know it already: there is a bug in the Castor > IntegerValidator. > > > > In method 'void validate(final Object object, final ValidationContext > context)' > > line 337 (Castor 1.1) should read > > > > value = ((Integer) object).intValue(); > > > > instead of > > > > value = ((Long) object).longValue(); > > > > Greetings > > Rudi Woehrl > > _______________________________________________________________ > > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
