You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2006/05/07 08:56:51 UTC
[jira] Resolved: (STR-1724) LookupDispatchAction and DispatchAction
getMethodName enhancement
[ http://issues.apache.org/struts/browse/STR-1724?page=all ]
Don Brown resolved STR-1724:
----------------------------
Resolution: Fixed
Assign To: (was: Struts Developer Mailing List)
I believe at least one of the dispatch action flavors supports an unspecified method. Reopen if this is still an issue.
> LookupDispatchAction and DispatchAction getMethodName enhancement
> -----------------------------------------------------------------
>
> Key: STR-1724
> URL: http://issues.apache.org/struts/browse/STR-1724
> Project: Struts Action 1
> Type: Improvement
> Components: Core
> Versions: Nightly Build
> Environment: Operating System: All
> Platform: All
> Reporter: Brandon Goodin
> Priority: Minor
> Attachments: patch.txt, patch.txt, patch.txt
>
> Rather than returning null with the getMethodName when a value is not specified
> it is preferable that it actually return a value. I am attaching a patch that
> causes the getMethodName to return "unspecified" rather than null. I wrote some
> custom Actions that were very similar to the LDA and DA because the LDA did not
> provide the neccessary hooks to get at certain information. Being that the
> getMethodName is protected it is available for use in extended actions. I just
> don't like the idea of having to do a null check in my code in order to get the
> string "unspecified" when it could be done in the LDA and DA action themselves.
> 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