After thinking through this issue much more deeply, I believe tapestry is behaving as expected keeping bad data out of my defined objects. I think I'll just need to rethink my approach. Perhaps there is a way to pull the bad value from the validation tracker?
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Clientside-validators-returning-null-value-to-serverside-validation-tp5719258p5719259.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
