Forwarded to user list. --- Jonatas Gustavo Rodrigues wrote: > It s ok, but if the return of an action method could > be an object, it can provides an implementation like
> View Handler of JSF. The default handler could be the > Struts one, but we could extend or change this code. http://cwiki.apache.org/WW/jsf-plugin.html (I don't know anything about JSF, so I have no idea if it does what you're talking about.) I guess in my opinion returning something other than a String from an Action makes testing, debugging, and configuration more difficult. My idea of (part of) the "command pattern" (XWork) is to allow trivial mapping from a result to the representation of that result. *That* is the most flexible place to implement something like what you're talking about. As soon as I'm returning a complex object from an Action I am tied to whatever it is I'm returning (a Tapestry component, a Swing dialog box, whatever). To eliminate that coupling, I return something built-in to the language. Now I can test easily and trivially reconfigure how that result will be represented in a running system. > Can we replace the StrutsDefaultInvoker ? That I don't know. d. ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
