Laine Donlan wrote: > > perhaps some time later nobody will remind old perform(), but would > use > > new execute() ;-) > > OK by me, especially if the controller were somehow smart enough to call > one or the other if both approaches were mixed in the same application > (during a migration period). > > - Isn't this kind of handled by having the base Action pass off to the > execute? > - This pretty much leaves it up to the application developer which > services to use?
I was thinking that anopther method, like execute() could just throw exception and be called by the ActionServlet, and the perform() form would not be called at all. So, like, deprecate perform() in favor of execute() (or something), if we can get the controller to gracefully choose between them. But I'm not sure how that would work ;-) -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
