DO NOT REPLY [Bug 29746] New: - DispatchAction.unspecified works for empty string but not null

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29746>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29746

DispatchAction.unspecified works for empty string but not null

           Summary: DispatchAction.unspecified works for empty string but
                    not null
           Product: Struts
           Version: 1.1RC2
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Standard Actions
        AssignedTo: dev@struts.apache.org
        ReportedBy: kenny_grimm@stchome.com


The LookupDispatchAction and DispatchAction 'unspecified' method will only be
called if the  handler parameter is set with a value not found in the mapping. 
Should this not also work when the parameter is not passed in at all?  The name
'unspecified' in a way implies that you could call the action without specifying
a handler parameter providing a default method.

For example, if my action is called searchUsers.do and the handler parameter is
'action':
/searchUsers.do?action=    will invoke unspecified
/searchUsers.do            will error on Request[/searchUsers] does not contain
handler parameter named action

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org