For the 1.2 users: I have a simple CRUD unit that I'm working on. Instead of creating an action for each one, I originally used DispatchAction to merge them all into one action. This allowed me to have my Create/Update page re-use the same JSP - I included a hidden param for the respective method and html:form just pointed to this Action. However, validation was applied for all operations, which I don't want for Read/Delete.
Now, my problem is inverted:
So, MappingDispatchAction looks like it lets me break out the Actions,apply validation to specific actions but still have all the code stored in one file. However, I can't see how I can re-use the same JSP for Create/Update now. <html:form action> used to call MainMethod.do, and pass the Method=Create along with it. Now, I have to call a specific .do for Create/Update, etc so this won't work.
Any ideas on where I'm going wrong? Is there something I'm missing for just DispatchAction that would turn the validate off when I don't want it?
Thanks,
- Nic.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
