DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23391>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23391 scaffold RelayAction: allow defined relay parameter name Summary: scaffold RelayAction: allow defined relay parameter name Product: Struts Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] org.apache.struts.scaffold.RelayAction currently requires the use of "dispatch" (Tokens.DISPATCH)as the request parameter name to use when finding an ActionForward. This is okay, but RelayAction would be hard to plug into an existing Struts application that used a different parameter name (like "method", as suggested in Mr Husted's book, no less!). So, why not allow RelayAction to do something like this: <action path="/savecustomerrelay" type="org.apache.struts.scaffold.RelayAction" name="customerForm" validate="false" scope="request" parameter="method"> <forward name="save" path="/savecustomerdispatch.do" redirect="false" /> <forward name="cancel" path="website.welcome" redirect="false" /> </action> Now, "method" is being used because it is set as the ActionMapping's "parameter" attribute. If "parameter" isn't specified, then RelayAction should fall back to "dispatch". Also, some logging for debugging purposes would be nice, like what relay name is being used and a dump of the found ActionForward. So, a patch is to follow. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
