While I think that would fix the problem having the DateField use the Lenient parser seems wrong to me. Would it make sense for the Integer validator to accept '123!4' as 12314? If the purpose is to validate dates then that's what it should do.
So I suppose a different fix is to replace the type converter with one that calls setLenient(false). I guess my question is what's the point of the default being lenient? -- View this message in context: http://tapestry.1045711.n5.nabble.com/DateField-appears-to-use-lenient-date-parser-Bug-tp5715631p5715637.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
