Patrick Lightbody wrote:
Well, that could then probably be rewritten as:I can apply some real-world examples here:I'm in a screen that is updating document metadata, and the form submits to UpdateMetadata.action. But UpdateMetadata.action is actually an alias for a complex chain: ValidateMetadata -> BeginTx -> StoreMetadata -> CommitTx -> StoreMetadataInHtmlFiles -> LoadMetadata -> showmetadata.jsp
ValidateMetadataProxy -> TxProxy -> StoreMetadataInHtmlFilesProxy -> StoreMetadata action
where SUCCESS = showmetadata.jsp and the JSP has an <action> tag pointing to LoadMetadata. Much nicer. Less code.
Are there any other cases where the "side-effects" *should be* "real actions", or could all of those be rewritten with action proxies?
/Rickard
-------------------------------------------------------
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