Correct me if I'm wrong, but isn't there only one real way to implement an action, and that's to implement "Action"? "ActionSupport" is an implementation of "Action", so by extending it, you by default implement "Action". So, only by implementing the interface directly or by extending an existing implementation can you get an action. AFAIK, the only standard implementation included in the project is ActionSupport. ServletActionContext has nothing to do with this; it's an implementation of ActionContext that contains some servlet specifics, and is usable from any implementation of Action. If you extend from ServletActionContext, it won't be a usable action.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Hernandez Sent: Thursday, September 25, 2003 4:58 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] WebWork2 best practices for creating Action Classes you can use ServletActionContext in your actions that derive from Action or ActionSupport Thompson, Kris wrote: > Looks like there are 3 common ways to create a WW2 action class > > Extending ActionSupport, extending ServletActionContext or > implementing > Action > > When should each one be called? > > IMO > > ActionSupport seems to be the best specially for web implementations > while still keeping developers away from the http response and request > > Action seems fine, more bare bones but doesnt have some of the helper > features like addFieldError that ActionSupport has > > ServletActionContext I guess should be considered a "last ditch > choice". IF you must have access to the request or reponse then it is fine. > > > > What is everyone elses opinion on those? Am I missing any other > common > ways to create Action classes? > > Thanks > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
