_eventName should override other event specifiers
-------------------------------------------------
Key: STS-568
URL: http://www.stripesframework.org/jira/browse/STS-568
Project: Stripes
Issue Type: Improvement
Components: ActionBean Dispatching
Reporter: Ben Gunter
Assignee: Ben Gunter
Priority: Minor
Fix For: Release 1.5
Prototype's Form.serialize serializes all the button and submit inputs in a
form, no matter which of the buttons was clicked to submit the form. This often
results in Stripes throwing and exception because more than one event name is
present in the parameters. We need some way to explicitly override that
behavior in Stripes and specify which event is intended to fire.
Currently, Stripes will honor the _eventName parameter only if there are no
other event parameters present. It first checks a special request attribute
(used for internal forwards), then parameters matching event names, then the
extra path info, and finally _eventName. I propose we change the order to
request attribute, then _eventName, then other parameters, then extra path
info. This would allow for use of Prototype's Form.serialize without any
hackish workarounds, as long as _eventName is present.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
