[jira] [Closed] (TAP5-1800) LinkSubmit/Submit should store event and context in ComponentAction

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1800.
--------------------------------------
    Resolution: Won't Fix

It is quite reasonable to create new components that have the desired behavior, using the existing ones as a template. Changing the behavior of these components is likely to have unforseen consequences.

> LinkSubmit/Submit should store event 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 was sent by Atlassian JIRA
(v6.3.4#6332)