On 1/23/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> I'm still not sure I see how this suggestion solves the problem... but,
> since three people seem to think it will at this point, I have to assume
> I'm just being dense... It happens from time to time ;)  Can you walk me
> (and I assume Paul and Rick, who have been in on this discussion) through
> it again?

Yes, I'm being dense also, since I don't see how providing a way to
customize the parameter name solves the problem. If someone figures
out the name of the your custom cancel parameter you are back having
the same problem, plus many won't even be aware there is an issue and
simply call the param "cancel" making it very easy to figure out.
Actually, since I've never used the cancel button (I prefer to submit
a cancel request with a reqular submi), I'm wondering does the param
name show up in the html source code? If so that really makes the
whole custom parameter name silly.

I really don't see a way to make a solution that will work nicely in a
backwards compatible fashion. I think maybe it will work if you force
users to provide an "canCancel" attribute in their action mapping.If
this param doesn't exist than the Action doesn't fire when a cancel
event is picked up by the RequestProcessor (or whatever is being used
in the latest version of Struts:)

The problem with this approach is that it's not really the ideal. I
still think the ideal is to simply look for a "cancel" method in the
action when a cancel is submitted. This means the user doesn't have to
worry about messing with another thing in the struts-config. They
simply code that "cancel' method if they need. Most people use
DispatchActions anyway so they'll be comfortable with this. Those that
don't use them, it would just be one method so I don't think it should
be that big of a deal.

I guess it becomes an issue of how important backward compatibility is.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to