Well, there are tonnes of use cases for this (you are talking about commands
right?)
The most commonly quoted one is a CRUD action. You create different methods
like doCreate(), doUpdate() and have the same fields (ie name, email etc).
For CRUD actions, I'd probably (with what I know of WW2 thus far), do this:
abstract public class CrudAction implements Action {
final public void setOperation(String operation) { ... }
final public String execute() throws Exception {
// switch on operation value
}abstract protected String create() throws Exception; abstract protected String retrieve() throws Exception; abstract protected String update() throws Exception; abstract protected String delete() throws Exception; }
Why do we need an Action to have multiple entry points? I still don't get it. Having the framework lock it into a single entry point does not prevent patterns of multiple entry point implementations.
I thought we were trying to get away from Struts... let's lose the "do" prefix :))
Erik
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
