Kjetil Paulsen wrote: >>The current code only calls validation if no command is set. >>Hm.. maybe >>this should be changed... what do ya'll think? > > Is there a reason not to?
Well, if the validation is specific to doExecute() it's bad. But, since we now have "isCommand()" it should be possible to do validation selectively. So, no, not that I can think of. /Rickard _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
