Dave Newton wrote:
--- Jonatas Gustavo Rodrigues wrote:
In this way, this object (like an UIComponent) could
be used for an> registered Result object to render
the result (this Tapestry).
I expect that you could create a result type mapping
from a String result to whatever you wanted, the same
way there are about a dozen different result types.
Returning a string makes testing and configuration
insanely easy... From
http://cwiki.apache.org/WW/result-configuration.html:
'An Action can pass back a token like "success" or
"error" without knowing any other implementation
details.'
This means that all your Action does is send back a
token. The command pattern *configuration* decides
what to do with that token, possibly rendering a JSP,
redirecting to a different S2 action, etc.
See also:
http://cwiki.apache.org/WW/result-types.html
Also note that if you really wanted to pass something like a UIComponent
instance to a result you could do so through the request scope or OGNL
value stack. And you can always render the response through whatever
means you want and return null, in the extreme case.
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
