In my project I group the CRUD actions for a table into a single dispatch action class.
I've found that sometimes I want the form validate to occur, sometimes I don't. To accomodate this, I always have to have two instances of my action mappings, one with validate set to true, the other to false. Have I designed poorly? The two action mappings are the same for everything except path name and validate. Situations where I don't want validations: 1. Browse screen -- displays the records 2. Calling add screen -- don't need validations to occur when calling the add form, only when submitting the add form 3. Calling edit screen -- again, it's only after an edit has occured an you submit the form do you validate. 4. Deleting a record -- since I'm deleting, I don't need field validation Situations where I do want validations: 1. Submitting the add form 2. Submitting the edit form I hope I'm being clear. For each table I have a single action that responds to all the CRUD events. I use dynamic validator form beans and the validator framework. I have one browse.jsp and one form.jsp for each of the tables. The same form.jsp works for the "add" and "edit" and "delete" use cases -- only the buttons differ. Thoughts? Lee --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
