> -----Original Message----- > From: Steve Conover [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2003 12:29 PM > To: [EMAIL PROTECTED] > Subject: Re: My Solution [Was: Re: Re: [OS-webwork] 'best > practices' around forms with multiple submit buttons9 > > > My latest solution is very similar. I name my submit buttons > saveCommand, cancelCommand, etc. I have an > ActionFactoryProxy that checks for a param with name > *Command. If that exists, it parses the first part of the > command name ("save" or "cancel"), and adds a new param to > the parameters map named "command" with the parsed name as > the value. Finally, it removes the *Command parameter from > the parameter map. > > Then I just use WW features - I have an Action class that > extends ActionSupport and implements CommandDriven, which has > methods like doSave and doCancel. >
Does anyone have any good ideas about better ways to make this standard in WW 2.0 using interceptors? Seems like something that would be good to standardize and put into the framework. > Which brings up a question about WW. I have the ability to > execute one of many commands as described above, so should I > be able to give each its own treatment in the mapping file? > > ex: > foo.action!save.success=someview.vm > foo.action!cancel.success=index.action > > -Steve > > You can do this already. Jason ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
