You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2006/12/02 22:25:58 UTC
[jira] Resolved: (STR-1771) [scaffold] RelayAction: allow defined
relay parameter name
[ http://issues.apache.org/struts/browse/STR-1771?page=all ]
Paul Benedict resolved STR-1771.
--------------------------------
Fix Version/s: (was: 1.3.6)
Resolution: Fixed
> [scaffold] RelayAction: allow defined relay parameter name
> ----------------------------------------------------------
>
> Key: STR-1771
> URL: http://issues.apache.org/struts/browse/STR-1771
> Project: Struts 1
> Issue Type: Improvement
> Components: Unknown
> Affects Versions: Nightly Build
> Environment: Operating System: All
> Platform: All
> Reporter: Ted J Schrader
> Assigned To: Paul Benedict
> Priority: Minor
> Attachments: RelayAction-dispatchParamPatch.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira