Paul Benedict wrote:
I think there could be 2 ways of doing this. Have a marker interface called CancelableAction which allows the behavior to be turned on; but ultimately controlled by the action mapping. This allows [1] the Java developer to specify the behavior with [2] the configurer to have final say.
This seems like more work to me than just the additional method in Action... Potentially having to deal with it in two places seems overly onerous to me, and potentially more trouble than it's worth... what if the configurer overrides what the Java developer intended and they don't communicate? For that matter, how often are the two not the same person anyway? I have no doubt it does happen, but how often?
At least in the 1.1.x and 1.2.x branches, all Actions must extend from Action, so adding the method would be fine, even for those of us using custom base Actions. It would cover everyone. In 1.3 the situation can be a little more complex as I recall, and I haven't thought about it a great deal.
The interface approach also doesn't give you one benefit the extra method does: that default implementation that does something intelligent. I think that alone is worth it.
What are your thoughts on that Paul?
Paul
Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
