[ https://issues.apache.org/jira/browse/TAP5-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689114#action_12689114 ]
Thiago H. de Paula Figueiredo commented on TAP5-597: ---------------------------------------------------- Isn't this issue covered by https://issues.apache.org/jira/browse/TAP5-146? > The form submit event handler method should have access to the source of the > event > ---------------------------------------------------------------------------------- > > Key: TAP5-597 > URL: https://issues.apache.org/jira/browse/TAP5-597 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core > Reporter: Hugo Palma > Priority: Minor > > Right now if you want to have more than one submit button in a form and you > want to implement different execution logic for each you have to: > - implement an event listener for both buttons that sets a local field that > signals which button was pressed. > - implement a form event listener method that reads the local field value and > executes whatever logic based on that. > (such a solution is provided on > http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/input/multiplesubmits1) > If the form event listener could know which button triggered the commit this > type of logic would be much simpler to implement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.