Hai Pham wrote: > Currently there are two minor usage problems with > CommandDriven factory. I will summarize them briefly > below. A patch is attached along in this email. > > 1. Command Name: > > Right now the name of the command is fetched from the > value of the submit button:
No it's not. It's fetched from any field with the name "command". I personally prefer to make it a hidden field. > 2. Recursive CommandDriven invocation: > > This happens when there is a "command" parameter in > the request's parameter list. This command is supposed > to be used by the action handling the form only. Now, > if within that action, you dynamically execute another > CommandDriven action, or within the view of that > action you use <webwork:action> or #action (velocity), > ww will set and invoke the same command. This is not > an expected behavior. Of course you can use > MyAction!myCommand to get around that, but right now > it doesn't seem to work with action alias. The quick > fix is to check if the action name ends with '!'; if > it does then we need not to set the command. This has to do with the more complicated problem of chaining actions, which is something that needs to be dealt with soon, agreed. /Rickard -- Rickard Öberg _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
