Anyone know why the error handling is different in these
two Action classes when the parameter is missing from
the request?
DispatchAction calls the unspecified() method, but
LookupDispatchAction throws an exception that can not
be caught in the application.
Why isn't LookupDispatchAction calling the unspecied()
method as well?
I wouldn't call this a bug (a very annoying feature, at
least for me), but from reading the javadoc for the
DispatchAction.unspecified() method, it looks like the
method was added in later to allow application developers
to create their own default behavior when the dispatch
parameter isn't specified. I think the same behavior
should be present in LookupDispatchAction as well.
Any comments?
-TPP
-----------------------------------------
This email may contain confidential and privileged material for the sole use of the
intended recipient(s). Any review, use, retention, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data corruption, interception,
tampering, unauthorized amendment and viruses. We only send and receive emails on the
basis that we are not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
