Shouldn't validation just be fixed?
The root problem is that validation only uses the action alias and
doesn't check if a method name is provided in a parameter.
The user of a wildcard just works-around that limitation to creating an
alias it can match.
For historical reasons there's at least two ways to specify which action
and method should be invoked but XML validation doesn't support both.
Perhaps it's not possible or too slow for the validator to examine the
ActionMapping though.
Dale Newfield wrote:
As evidenced by the diffulties described on the user list in "Wildcard
mapping should not suck (but does)", I propose that instead of having a
method attribute on the submit tag that works w/o js in the client, but
requires some black magic on the server side, we add an "action" attribute
to the submit tag that uses js on the client to change the form target
before submitting. This will enable the usage pattern that I believe
developers want and reduces the dispatcher complexity.
Thoughts?
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
