Josh, Thanks a ton... very much appreciated. This is exactly what I was looking for. My form consist of about 20/30 fields, so I don't think I'll see much of a performance issue using option 1. As far as option two, I wasn't aware tapestry allowed us to pass back a value through the parameter variable. Great to know, you answered my question how to map a field with the isDisabled method. Anyhow thanks again.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-dynamically-set-disabled-attribute-tp2414476p5032387.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
