this is how tapestry works. field-level validations of one field are not known to other fields.
we have a similar situation where we wanted to avoid DTOs and use Domain Objects (the exposed domain pattern). we find that the underlying objects can get dirtied in a number of ways. validation is just one such scenario. tacos ajax submits also cause transient values to be set. it's something you've to live with. just ensure your data does not make its way to the DB :-) On 8/10/06, Tim Sawyer <[EMAIL PROTECTED]> wrote:
I have a page which has mandatory validation on some of the fields. If I leave mandatory values blank, and change the value in other fields, when the form is submitted the changed values seem to be updated in the model even when errors are shown for the mandatory values. If I then leave my screen using a cancel button, the model has been updated for the values that were changed. Is this expected behaviour? Ideally the behaviour required is for none or all of the fields on the form to be updated, i.e. none if there is an error, or all if there is none. Can I get this behaviour? Cheers, Tim. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thanks, Karthik
