LinkSubmit/Submit should store evet and context in ComponentAction
------------------------------------------------------------------
Key: TAP5-1800
URL: https://issues.apache.org/jira/browse/TAP5-1800
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.3, 5.4
Reporter: Michael Wyraz
When using multiple LinkSubmit (e.g. in a Loop), the event and context from the
last one is fired, independent of which is clicked.
The reason is that the parameter "event" and "context" are determined during
the execution of the ComponentAction by accessing the component's fields. So
when the acion is defered (which is default), these fields contain the values
from the last usage of the component. A workaround is to det defer=false.
To fix it, simply store "event" and "context" to the process submission (beside
the clientId which is already there).
The same issue might apply to Submit, it has the same code (untested).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
