I've also used the ! notation extensively, and am disappointed that it
is being removed. I find that the 1-1 mapping from the URL to the
method on an action is simple to follow and easy to understand.
One thing that I have not seen any mention of yet is conflicting
mappings - what happens? Which has the priority? What happens if larger
application want one to take preference in one circumstance, and a
different one under another scenario? I would argue that a sufficiently
large application has not been converted to ensure these issues would
not arise.
As it stands in this moment in time, we have a switch around the !
idiom, because it is a security flaw that people need to understand
before enabling, and that's all.
I have to say that I still don't really understand why this is a
security flaw. I can understand that calling any public method on a
class may not be a good thing, but let's face it, actions are *meant* to
be called via a URL. If there is a security issue - then it is an
application security issue - because the method is NOT doing the
required checks to ensure this is a valid request.
On more of an implementation / existing knowledge approach - if this is
a Stuts to Struts2 conversions, then there will only be one method, the
execute() method. If this is a WebWork to Strut2 conversion then the
developers should be aware that this feature is available.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
